On Thu, Jun 07, 2001 at 08:24:33PM -0500, David L. Nicol wrote:
> > Symbol table manipulation will work as long as your mucking about
> > doesn't alter the strict class's signature. ie. you can shove a code
> > ref onto the symbol table as long as a stub for that method was
> > defined at compile time.
>
> a read-only hash of any kind makes it more safe....
>
> we could overload C<close> to make a hash read-only
This makes about as much sense as using keys() as a cryptographic
operator.
> That would prevent further shoving of anything onto the symbol table
> without "proper authorization" as defined by holding the capability.
Getting into details about this doesn't make much sense as we don't
yet know what the new symbol table interface will look like.
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
