Interesting that you mentions this. For debugging the compiler, maybe. I
find however that when working in a language, any language, I want my
debugger to point to source locations in the source I wrote, and not in some
generated intermediate language that I don't care about for getting the job
done. ANTLR is a great example of this. Debugging an ANTLR grammar is hard
work due to the extra step I need to go through to map the locations my
debugger tells me to the actual locations in the grammar when I single step
through the parser.

/Tobias

On Sun, Nov 22, 2009 at 7:30 PM, Matt Fowles <[email protected]> wrote:

> Robert~
>
> Ease of debugging mostly.  Our production environment always goes straight
> to bytecode, but when we are debugging the compiler it is much nicer to be
> able to step through java code and get links from it back to compiler code
> the generated it.
>
> Matt
>
> On Nov 22, 2009 1:15 PM, "Robert Fischer" <
> [email protected]> wrote:
>
> What, exactly, is gained by compiling to Java and then compiling the
> Java to bytecode?  Are there optimizing compilers out there for Java
> source code => byte code that you can leverage?  If not, then is there a
> particular example of a place where it's easier to generate Java code
> than byte code?  I just don't see what you're gaining, although I'm
> intrigued.
>
> ~~ Robert.
>
> [email protected] wrote: > > Some jvm languages have problems left to
> solve: > > -------------...
>
>  --
> You received this message because you are subscribed to the Google Groups
> "JVM Languages" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<jvm-languages%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/jvm-languages?hl=.
>

--

You received this message because you are subscribed to the Google Groups "JVM 
Languages" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/jvm-languages?hl=.


Reply via email to