Re: Heron.NET or JHeron?
Posted: Dec 13, 2004 4:07 PM
> Chris -
> As someone planning on targeting a compiler to the JVM and
> having studied it a fair amount, I'd like to point out
> that it's not very flexible. The types it supports are
> pretty limited and would be pretty difficult to extend
> value types and make it work properly. Also, all objects
> must derive ultimately from System.Object. Primitives are
> always passed by value, everything is always passed by
> reference. As far as I can figure, this stuff is hard
> coded into the VM itself, and violating the VM semantics
> winds up with the VM rejecting the binary.
I appreciate the concern, but I have studied the JVM at great length as well. Like any kind of port / translation, the obstacles can always be overcome (i.e. by generating utility classes or by creating an emulator). It is simply that the mapping is non-trivial. This is the case for translating Heron to any target, and was the same for even porting it to C and C++, despite the syntactic resemblance.
In other news, the YARD parser is now online at http://www.codeproject.com/useritems/yard-tokenizer.asp