On Sep 4, 2008, at 7:02 PM, Charles Oliver Nutter wrote:
>> The only difference is that the class name as generated would
>> probably
>> be $$autogenerated$$0fc45e9a or something of similar beauty, and not
>> "Complex" :-)
>
> Perhaps it's time for an analog to JSR-42 that provides a mapping from
> mangled class and method names to actual names.
Well, in my original example, I would've expected the runtime to
create a class out of two object literals, {re:5,im:6} and {re:7,im:
9}. I would be highly surprised if you could have a compiler deduce a
non-mangled name out of these :-) (best it could come up with would be
"ReIm", IMHO; or "re_int$im_int").
> I've got a "hybrid"
> stack trace generator in JRuby right now that mines
> StackTraceElement[]
> for known interpreter calls and replaces them with information from
> interpreter frames:
Yeah, we have something similar in Rhino too, except we use it for its
stackless interpreted mode, where it uses a linked list internal stack
within a single interpreter invocation -- we're replacing
Interpreter.interpret() stack trace elements with JS stack produced by
their invocation...
Attila.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "JVM
Languages" group.
To post to this group, send email to jvm-languages@googlegroups.com
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=en
-~----------~----~----~----~------~----~------~--~---
