> It means a lot more code to write (and debug) for the things that > return these objects, and that means parts of perl will be > slower, take longer to write, and take up more space. Point taken. I don't think internals should be ignored altogether, just that they shouldn't be the driving force in the language design. Otherwise we'd wind up with something like C. :-) One alternative is to add a pragma to implement this, maybe called 'object'. So a person could 'use object' to get the objects flowing everywhere. But again, this is an implementation thing I'd rather save until at least v2, after people have given input on the idea itself. -Nate
- RFC 73 (v1) All Perl core functions should return ob Perl6 RFC Librarian
- Re: RFC 73 (v1) All Perl core functions should re... Dan Sugalski
- Re: RFC 73 (v1) All Perl core functions shoul... Mike Pastore
- Re: RFC 73 (v1) All Perl core functions s... Dan Sugalski
- Re: RFC 73 (v1) All Perl core functio... Nathan Wiger
- Re: RFC 73 (v1) All Perl core fu... Dan Sugalski
- Re: RFC 73 (v1) All Perl cor... Nathan Wiger
- Re: RFC 73 (v1) All Perl... Dan Sugalski
- Re: RFC 73 (v1) All Perl... Nathan Wiger
- Re: RFC 73 (v1) All Perl core functions s... Johan Vromans
- Re: RFC 73 (v1) All Perl core functio... John Porter
- Re: RFC 73 (v1) All Perl core functions shoul... Ken Fox
- Re: RFC 73 (v1) All Perl core functions s... Mike Pastore
- Re: RFC 73 (v1) All Perl core functions shoul... Chaim Frenkel
- Re: RFC 73 (v1) All Perl core functions s... Peter Scott
- Re: RFC 73 (v1) All Perl core functions s... Dan Sugalski
- Re: RFC 73 (v1) All Perl core functio... Nathan Torkington