On Mon, Aug 09, 2004 at 08:53:27AM -0400, [EMAIL PROTECTED] wrote: > - MQ has constants. Thousands of them. In the perl module, these get > mapped to perl XS subroutines (which bloats the symbol table no > end). For parrot, I'd prefer to use two big hash tables of the type
As in at load time every constant is newXSproto for a new subroutine, with all created at compile time? Do most constants get used by most code? Does the AUTOLOADed approach generated by h2xs use even more memory or have other problems (eg I know that it doesn't define its subs with a ($) proto, which means that the constants won't be inlined by the peephole optimiser) [Ignore whether h2xs will merely barf, or barf horribly on your headers. I was wondering about the approach] > I'd prefer to optimize for smallest data structure size, and am > willing to take a minor hit at lookup time; looking up constants is > not performance-critical. Yes, my questions are more perl5 related, so are sort of really off topic, but I'm wondering what mistakes the current perl5 implementation has. Should I have cross posted this to p5p and used reply-to to prod follows over there? Nicholas Clark
