On Sun, Mar 05, 2006 at 02:53:29PM -0600, Joshua Isom wrote: > > On Mar 5, 2006, at 1:46 PM, Nicholas Clark wrote: > > >On Fri, Mar 03, 2006 at 11:27:05AM -0800, Allison Randal wrote: > > > >Should the network opcodes even be loaded as standard? C<socket> et al > >aren't > >actually that useful on Perl 5 without all the constants in the Socket > >module, > >so in practical terms a redesigned Perl 5 would do better to remove > >all the > >socket specific keywords and make them functions exported by the Socket > >module. Should parrot go the same way? > > A pasm include, such as the signal.pasm(even though signals don't work > yet), would suffice and is generated at compile time. Parsing .h files
This way does the numeric values of the constants (at compile time) get frozen into bytecode written out to disk? Or does the generated bytecode do the lookup at run time on the run time platform? Nicholas Clark
