>>>>> "AT" == Adam Turoff <[EMAIL PROTECTED]> writes:
AT> If Perl bytecode were to become threaded, it would be rather troublesome.
AT> It would probably require some attribute or early compile time
AT> declaration (in main::BEGIN) to tag specific subs/builtins to be
AT> overridden at runtime. It would also force a runtime error when
AT> attempting to override a threaded sub; that it can't be overridden
AT> anymore violates the principle of least surprise wrt Perl5.
AT> It would also mean that if anything was overriden anywhere, no
AT> module code could be read in as bytecode, since it may need to be
AT> rethreaded to incorporate overrideable subs/builtins.
I'm missing something here.
Wouldn't just the appearance of *foo = \&other_foo, be enough to tell
the compiler to treat all foo's (or perhaps if there were some dataflow
analysis some region of code) to use indirection?
<chaim>
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
