Science > Physics > Java is Used to Write a Compiler- for the first time.
| Topic: |
Science > Physics |
| User: |
"Douglas Eagleson" |
| Date: |
11 Oct 2005 07:34:51 PM |
| Object: |
Java is Used to Write a Compiler- for the first time. |
Java May Be Used to Write Compilers.
(warning this is all abstract form of applied inference.)
A java compiler class is able to be written now that
the preceding theory of abstraction class is written. I
wrote the Class Model to allow the abstraction itself
to be modeled. A certain abstraction is the compilation.
And the foundation class called Compiler is designed.
class Compiler extends Model{
Object solution;
void Compiler(){
}
}
A main instance of Compile, is to cause the reference to
the abstract instance as the mean of correct symbol to
machine state relation.
A parameter to solve the function then names.
So parameter is named, solution.
Model parameter.model
Compiler solution.compiler
A reference to the instance's compiler is to cause
the compilation symbol. A java class.
And the class is the symbol as the implementation.
A true self writting is to be demonstrated.
A proposed test compiler design is to be defined:
A state machine is altered as the symbol is referenced.
And the solution to the name
void Compiler/main(){
Complier compiler=newCompiler();
solution.compiler=compiler;
//a state of compiler is to exist as its own object.
}
A simple main was written to demonstrate the symbol
generation of the correction compilation. A self reference appears
the reference. An Object type for, compiler, validates the
symbol machine state.
Abstract machine state is a parameter state, making the
Java Language and implementation a valid simulation.
And so to compile the code becomes the class generator.
And the self generation is demonstrated as the simplist
symbol for the code of all symbol to all parameter. A typing
validity then causes the new compilation to equal the
function of equation.
A solution to automatically generate the functional relation is to
write the abstract type class and solve for the correct type to
name. A selection of the correct type then becomes a sequential
validity test of the Types named parameter.
A class Type is to extend Compiler
And list all the types of Java as the parameters of Type's
arrary typename[] !!!!!!!!!!!!!!!!!!!!!!!
//remember the class Model still validly tempates the main constructor.
//and remember to name the parameter of Type by the theory of all
Model.
class Type/main(){
for(i=0;i<typelimit;i++){
Type type = new Type();
typename[i].type.compiler=type;
}
//catch invalid class references until the correct is found!
Complier compiler = new Compiler(Object typename);
//and here the name Object.object is the true genius of the
Java language.
}
A function is defined by the valid selection of the abstract type name.
Merely selecting the class instance parameter identical to
parameter.Compiler
define the abstract typeing solution.
A return of i.type solves the name of the parameter called solution.
An implied relation of any i exists for the class defined variable
applied
for the first time. i.type is a real relation of the java language or
implied by
reference validity.
A symbol of type in the array typename is to cause the naming of
typename itself!!!!!!!!!!!!!!!!!
Object typename; in class Type
and the reference return is defined as always the solution type for
the instance called compiler!!
Making the class Compiler require the input of objecttype for the
correct valid kind of solution.
A type for solution.compiler is then defined as the correct type to
solve the array reference typename[i] as the valid symbol related to
the valid instance of parameter type.
Making the Compiler class input the kind of Object. A class parameter
called solution.compiler is to be name referenced by the Java theory
of abstract Object reference.
A type of class input Object typename is to cause the kind of Object.
And so the hard part to the function of compiler design is finsihed.
Once the typename causes the reference function value and the
type of instance a true compiler is designed.
Merely testing the validiy of the abstract Model naming controls
the design of even the abstract compiler.
Type solution is demonstrated. And now that the type is declared as
the solution to the symbol.object dilemma, a correct applied
abstraction is
has this compiler implementation as the truth test.
A naming convention as the inference Model assisted the inference of
class parameter naming for the instance of inference called
compiler.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Douglas Eagleson
Gaithersburg, MD USA
If the correct abstract relation truly defines this compiler then the
amazing magic of the C and other compilers is hereby discovered.
I like the basic model of Java, but hate the irrational class usage.
And to self compile the compiler appears the symmetry of any true
symbol causality in general. A state of reference causes the state's
inference's instance existence.
A very, very hard analysis is written and the claim to compiler
validity
as a truth of inference form is the intention of the writer.
And so when all object's cause a valid inference a kind of relation
was discovered in example, but was never quite correctly
abstract. The naming convention of objective applied form
for Java was never correct. It is now.
Subjective application of Java is a wholely separate school of
applied form.
Objective Java is the correct model of the scheme of naming.
.
|
|
| User: "" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
13 Oct 2005 03:51:01 AM |
|
|
download link, please? no? I thought so.
.
|
|
|
| User: "Douglas Eagleson" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
13 Oct 2005 02:26:09 PM |
|
|
wrote:
download link, please? no? I thought so.
No, I am still trying to determine the theoretical compiler symbol in
relation to the class of java. I am just blowing hot and cold air
right now and hope to actually make a simple compiler using java.
I made only the type test. And to make it further is to decide on the
exact classes of implementation.
Here is a possible full implementation outline:
A symbol set is defined in relation to the state. And to validate this
set, a certain file contents is referenced as a class parameter.
And here is where perfect compiler theory collides with the
preprocessor implementations commonly found. A state of the compiler
as the type integer index is an implemetation state, while the class
itself is to be the compiled program.
This is all hot air unless you really care about the abstract theory of
architecture, btw.
A symbol of the class bytecode as the state and the type reference i,
implies the ability to output the i as the compiler output? or is the
state of the ith type instance to be the compiled type?
Meaning a printing or the bytecode becomes the compiler's output?
And here is the true test. A relation of type in bytecode must be
translatable to the class as the string of symbols(a class in text), or
as the bytecode itself representing a state?
Meaning the virtual machine must recognize the bytecode as a symbol
pointer. And I need to go to the reference on the virtual machine to
see if the object itself is a class or symbol input.
So say I am full of Hot air in general, but my desire is to avoid the
fake self compilation. A preprocessor of the kind of any compiler is
the common compiler. And the model of the virtual bytecode is critical
to my ultimate success.
Even so I can always call the simulated compiler a success, because
java has a naming theory consistent with the compiler's need.
And so I must then only call a class output to the extent the bytecode
can implement the type the valid simulated compiler.
So all my applications must write the bytecode as strings!!!
And the textfile to class file translation becomes the degree of
simulated success.
And the arguement over the perfect theory of the compiler waits for the
day I generate binary from the java string.
And to then call the byte the reference of the state of reference is
the theory itself demonstrated by my first compiler example.
Thanks for reading if you are reading this.
MY index i as the type of type appears the state, and reference, the
instance tested. I speak of the original posting, btw. Making my
compiler output to the formal text file the only omisssion.
And it is trivial to make the bytecode for the type as the output and
the i as the reference in bytecode also. This is the output inversion
of the compiler in example.
Douglas Eagleson
Gaithersburg. MD uSA
note: the set of state as the binary is to be my first implementation
as the true bytecode compiler. A instance of typeing must only cause
the virtual machine runtime of the typing for the symmetry to be
existent. And consistent
symbol to type symmetry is the har compiler writing part.
A set of state in three abstractions to the shift of the bit as the
element of bit state is a dream of mine. I want to make the simple
cryptographic engine compiler. And all I need is to have the symmetry
maintained for perfect validity and speed.
A set as the symbols in the accessed file then becomes the hard part. I
think I will leave the compiled class instance as the limit of the
compiler. This way the code of class, transformation, is implemented in
an easy fashion.
And the compiler to only perform the state set transformation is almost
rivial to write then. All the overhead bytecode as class templates in
bytecode is therefor not to invalidate the theory of the compiler. A
symmetry of abstract template was assured by the correct class Model.
.
|
|
|
| User: "" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
14 Oct 2005 01:02:56 AM |
|
|
Douglas Eagleson wrote:
This is all hot air unless you really care about the abstract theory of
architecture, btw.
...
Thanks for reading if you are reading this.
yeah, well, in your class-naming(?) message I told you that you should
use down-to-earth terms, but you refused/failed to do so. your
abstractions cannot be understood by anybody before you do that :( we
need at least analogies or smth.
.
|
|
|
| User: "Douglas Eagleson" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
14 Oct 2005 10:26:14 AM |
|
|
I went through the theory in predicate. And the ability to clarify the
class terminology depends critically on the concept of abstract
inference. It is a very short review of the whole subject of form for
the computer.
If I clarify the subject in predicate the question will still arise. A
property of abstract inference form is the appearence of predicate
dilemma. An abstract dilemma is your problem.
Think of the subject of all formal logic in relation to the accepted
first order theory. And I claim a larger theory than first order,
exists. So it is a hard concept to handle, but the
down to earth subject of compiler theory is as close to simple as the
subject will ever exist.
So sorry for the confusion. I hope to have a small compiler example
written by the end of the year. And it is intended to demonstrate
abstract inference as the critical theory in the debate over formal
logic.
My one statement compiler example does exist for class theory study
purposes though. A larger set of example classes is the obvious need
though.
Thanks for trying to read though.
Douglas Eagleson
Gaithersburg, MD USA
.
|
|
|
| User: "" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
18 Oct 2005 07:22:14 AM |
|
|
Douglas Eagleson wrote:
...the
down to earth subject of compiler theory is as close to simple as the
subject will ever exist.
and that is wrong.
look, I am now going to speak to you in down-to-earth terms, so that
you would understand what it is.
let's say two guys, John and Bob, share two common concepts, basic1 and
basic2. besides that, John knows basic3, and Bob knows basic4. the
nature of human thinking implies both John and Bob will develop their
concept systems by abstracting them. that is, John can create abstract1
based on basic1+basic3, and Bob can create abstract2 based on
basic2+basic4. At this point, they will have major difficulties talking
about, because each one only understands a half of what every other
does. if we push it further, John might have abstract1, abstract3 and
abstract4 concepts, while Bob has abstract2 and abstract5. They now can
abstract it again (say, highly_abstract1 for John, and highly_abstract2
for Bob), and at this point they virtually do not understand each
other, and creating a common hyper_abstract based on
highly_abstract1+highly_abstract2 is impossible, until they do. in
order to do it, they will have to go back, down to basic*-s, and
exchange basic3 and basic4.
So, to be plain, put forth some basics we are missing here, or go away.
.
|
|
|
| User: "Douglas Eagleson" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
18 Oct 2005 01:03:01 PM |
|
|
The solution to the bob as the dilemma for the abstract button is times
five the dilemma of nobody.
Attacking the abstract form thinker will not work sometimes. You need
to solve your truth paradox to claim prefect logic form.
It is a simple as that.
Down to earth in your terms is a nice rendition.
.
|
|
|
| User: "" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
19 Oct 2005 02:17:13 AM |
|
|
Douglas Eagleson wrote:
Attacking the abstract form thinker will not work sometimes. You need
no, I do *NOT* need anything.
*you* came here first, you've posted tons of words noone understands,
and you refuse to explain yourself.
Down to earth in your terms is a nice rendition.
do we have a fight here? I thought you posted your stuff because you
wanned some feedback from public, but, the way this situation
developes, it seems that you don't :(
there's nothing more to do about it, so I am now unsubscribing...
.
|
|
|
|
|
|
|
|
|
| User: "Helmut Wabnig EmailAddress" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
13 Oct 2005 04:28:38 AM |
|
|
On 13 Oct 2005 01:51:01 -0700, wrote:
download link, please? no? I thought so.
A compiler written in Java,
written in C++ written in C+ written in ancient 16 bit C.
Assembly language is unknown at Micro$oft, is it?
Therefore they produce slow and overbloated junk.
I once thought, my Epson printer software is crap -
unti I bought a Hewlett Packard printer.
It came with 150 Mbyte printer supporting software written in JAVA.
Now I know how good the good old Epson was.
Hewlett Packard is a piece of *****,
JAVA is *****.
w.
.
|
|
|
| User: "" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
13 Oct 2005 10:08:47 AM |
|
|
Helmut Wabnig wrote:
On 13 Oct 2005 01:51:01 -0700, wrote:
download link, please? no? I thought so.
A compiler written in Java,
written in C++ written in C+ written in ancient 16 bit C.
Assembly language is unknown at Micro$oft, is it?
Therefore they produce slow and overbloated junk.
I once thought, my Epson printer software is crap -
unti I bought a Hewlett Packard printer.
It came with 150 Mbyte printer supporting software written in JAVA.
Now I know how good the good old Epson was.
Hewlett Packard is a piece of *****,
JAVA is *****.
Java was originally written to be a
virtual language. So why people apply
it to printers is unexplainable.
Sun mostly like made a call to AT&T
to enChina the code.
w.
.
|
|
|
|
| User: "A.L." |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
13 Oct 2005 09:33:29 AM |
|
|
On Thu, 13 Oct 2005 11:28:38 +0200, Helmut Wabnig <EmailAddress>
wrote:
On 13 Oct 2005 01:51:01 -0700, wrote:
download link, please? no? I thought so.
A compiler written in Java,
written in C++ written in C+ written in ancient 16 bit C.
Assembly language is unknown at Micro$oft, is it?
Therefore they produce slow and overbloated junk.
I once thought, my Epson printer software is crap -
unti I bought a Hewlett Packard printer.
It came with 150 Mbyte printer supporting software written in JAVA.
Now I know how good the good old Epson was.
Hewlett Packard is a piece of *****,
JAVA is *****.
Too hard for you to learn?... Pity....
w.
***** is this what you are writing. Where is this 150 MByte?... And
what is "printer" that come with a printer?..
A.L.
.
|
|
|
|
|
| User: "A.L." |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
13 Oct 2005 09:31:23 AM |
|
|
On 13 Oct 2005 01:51:01 -0700, wrote:
download link, please? no? I thought so.
This was computer generated message. Some gyus are trying to program
computer to generate "scientific" texts about java and are making an
attempt to have this paper accepted on a conference or to get NSF
grant.
A.L.
.
|
|
|
| User: "" |
|
| Title: Re: Java is Used to Write a Compiler- for the first time. |
18 Oct 2005 07:26:11 AM |
|
|
A.L. wrote:
This was computer generated message. Some gyus are trying to program
computer to generate "scientific" texts about java and are making an
attempt to have this paper accepted on a conference or to get NSF
grant.
interesting idea (note to myself: try that myself another day)
.
|
|
|
|
|
|
|
Related Articles |
|
|
