"Anthony Green" <[EMAIL PROTECTED]> writes:
> Tom wrote:
> > I think ideally the preprocessor would simply comment out lines
> > instead of removing them. That way the line numbers match with the
> > original source.
>
> It seems to be a very simple matter to post-process the preprocessor outpu
Tom wrote:
> I think ideally the preprocessor would simply comment out lines
> instead of removing them. That way the line numbers match with the
> original source.
It seems to be a very simple matter to post-process the preprocessor output
containing #line directives into a properly spaced file
On Sat, 23 Jun 2001, Tony Kimball wrote:
> Quoth Anthony Green on Saturday, 23 June:
> :
> : Any ideas/opinions?
> :
>
> ClassName.jpp -[cpp]-> ClassName.java -[gcj -C]-> ClassName.class -[gcj -o]->
>ClassName.o
cpp produces `#' lines, which aren't valid in Java source. [I don't know
wheth
Quoth Anthony Green on Saturday, 23 June:
:
: Any ideas/opinions?
:
ClassName.jpp -[cpp]-> ClassName.java -[gcj -C]-> ClassName.class -[gcj -o]->
ClassName.o
___
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpat
> Anthony Green wrote:
>
> I'd like to experiment with creating different runtime profiles,
> similar to the J2ME profiles for embedded systems.
>
> This will require different versions of some of the core classes (no
> floating point, no finalization, etc). I can just copy the .java
> files
"Anthony Green" <[EMAIL PROTECTED]> writes:
> I'd like to experiment with creating different runtime profiles,
> similar to the J2ME profiles for embedded systems.
>
> This will require different versions of some of the core classes (no
> floating point, no finalization, etc). I can just copy t
I'd like to experiment with creating different
runtime profiles, similar to the J2ME profiles for embedded
systems.
This will require different versions of some of the
core classes (no floating point, no finalization, etc). I can just copy
the .java files and maintain different versions -
7 matches
Mail list logo