Re: question on java lang spec chapter 3.3 (unicode char lexing)
On Wednesday, January 2, 2013 5:27:21 PM UTC-8, Aryeh M. Friedman wrote:
Well - since he is writing a lexer for Java then ...
A little more on the project... while the over all project *IS* for fun a=
few components may find there way into more serious work related projects =
but only to be used on code written by me or others on my team... specifica=
lly we may use the lexing/parsing component to make the following tools (th=
e actual code generation/etc. of the compilation is currently purely fun [s=
ee note]):
And your team can't use a real Java compiler because ... ?
1. Scan for a complete list of classes referenced by a given class (our b=
uild system sometimes hiccups on not realizing that when class X calls an i=
nstance of class Y and Y has been modified it needs to recompile X {if, and=
only if, the signature(s) have changed})
There are standard build systems that handle this. What do you use?
2. Do some minor style enforcement like warning (have not decided if it s=
hould reject or just warn) if a class/method does not have something that a=
t least looks like a javadoc header comment (/** ... */ is sufficient for t=
his purpose)
Lint. Findbugs. And more. Why reinvent the wheel?
Note:
A long term personal project of mine is to write a OS completely from the=
ground up in a super set of Java (the only addition I see that is needed i=
s some type of "safe" pointer type)... in this case safe being defined as y=
ou can assign a literal address to it but your not allowed to do ptr math o=
n it
Also known as "a JVM"?
--
Lew