2000-09-27-15:08:10 Simon Cozens: > Never too late to withdraw, sir. [1] The less crap we make Larry > wade through, the better. Regarding the specific issue at hand, could you please offer something more specific than "you'd like it withdrawn"? Is there a reason why it's impossible to implement without performance penalty, or why it must have a detrimental effect on the language? I'd cite ruby as an indication that it shouldn't have to inflict any performance hit, and ruby, as well as the obvious utility of bringing to bear O-O overloading techniques, as benefits it could offer the language. And I don't see why it has to be an obtrusive change at all. -Bennett
- RFC 161 (v4) Everything in Perl becomes an object. Perl6 RFC Librarian
- Re: RFC 161 (v4) Everything in Perl becomes an ob... Simon Cozens
- Re: RFC 161 (v4) Everything in Perl becomes a... Piers Cawley
- Re: RFC 161 (v4) Everything in Perl becom... Bennett Todd
- Re: RFC 161 (v4) Everything in Perl becom... Matt Youell
- Re: RFC 161 (v4) Everything in Perl b... Simon Cozens
- Re: RFC 161 (v4) Everything in P... Bennett Todd
- Re: RFC 161 (v4) Everything ... Simon Cozens
- Re: RFC 161 (v4) Everyth... Matt Youell
- Re: RFC 161 (v4) Everyth... Simon Cozens
- Re: RFC 161 (v4) Everyth... Nathan Wiger
- Re: RFC 161 (v4) Everyth... Simon Cozens
- Re: RFC 161 (v4) Everyth... Bennett Todd
- Re: RFC 161 (v4) Everyth... Simon Cozens
- Re: RFC 161 (v4) Everything in P... Matt Youell
- Re: RFC 161 (v4) Everything ... Simon Cozens
- Re: RFC 161 (v4) Everyth... Matt Youell