At 08:35 PM 8/6/00 +0000, Nick Ing-Simmons wrote: >Ken Fox <[EMAIL PROTECTED]> writes: > >(And if > >we say something like "this is fast" people will ignore all the warnings.) > >As one of the worst offenders I certainly will ;-) Works for me. :) People have always had the capability to fundamentally mess with perl, and this really isn't any different. (If your perl module had an XS component and loaded in first, you could completely remap what all the opcodes did, not that anyone ever went this far) Just better documented and with clearer lines around the "implementation may change" parts. Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- RFC 35 (v1) A proposed internal base format for perl Perl6 RFC Librarian
- Re: RFC 35 (v1) A proposed internal base format f... Nick Ing-Simmons
- Re: RFC 35 (v1) A proposed internal base form... Dan Sugalski
- Re: RFC 35 (v1) A proposed internal base ... Ken Fox
- Re: RFC 35 (v1) A proposed internal b... Dan Sugalski
- Re: RFC 35 (v1) A proposed internal b... Nick Ing-Simmons
- Re: RFC 35 (v1) A proposed inter... Dan Sugalski
- Re: RFC 35 (v1) A proposed internal base format f... Larry Wall
- Re: RFC 35 (v1) A proposed internal base form... Dan Sugalski
- Re: RFC 35 (v1) A proposed internal base form... Chaim Frenkel
- Re: RFC 35 (v1) A proposed internal base ... Larry Wall
- Re: RFC 35 (v1) A proposed internal b... Nick Ing-Simmons
- Re: RFC 35 (v1) A proposed inter... Larry Wall
- Re: RFC 35 (v1) A proposed i... Nick Ing-Simmons
- Re: RFC 35 (v1) A propos... Larry Wall
- Re: RFC 35 (v1) A propos... John Porter
- Re: RFC 35 (v1) A proposed i... Dan Sugalski