Issue OBJS124 (performance: Symbol type) has just been modified by user rob...@ma...
You can view the issue detail at the following URL:
<http://icandy.homeunix.org:443/scarab/issues/id/OBJS124>
The following modifications were made to this issue:
if each symbol has a unique-id, then we can use and int<->int hashtable to map member symbol to slot.
Or, another interesting possibility is for the compiler to generate (perhaps as inner classes) classes implementing a MemberTable (?) interface (see OBJS116), which could use switch statements instead of actual tables... need to investigate the performance of this vs. hashtables, and verify that the overhead of the extra classes created isn't too bad. Also, with switch statements, you don't need to create members in the hashtable, so the compiled code can createMemberBySlot() and getMemberBySlot(), without touching the table at all (because the compiled code already knows the contents of the table... which is just there for the benefit of resolving variables which can't be statically resolved.
|
