Re: RFC 161 (v2) OO Integration/Migration Path

"Randal L. Schwartz" wrote:
> 
> That's my first gut reaction to this proposal.  "If you like Python,
> you know where to find it, but let us have some primitive data types
> in Perl that act primitive so we can optimize things."

Well, we're on a border here. What this RFC is really referring to is
embedded objects, which are wholly different from objects stacked on top
of simple variables.

If everything uses these methods, then these methods *are* the internal
representation of data, meaning there's no slow down with builtin data
types. If you add your own class that grabs these methods, you pay when
you override one, but you don't when you don't. 

These messages talk about this concept thoroughly:

http://www.mail-archive.com/perl6-language-objects%40perl.org/msg00097.html
http://www.mail-archive.com/perl6-language-objects%40perl.org/msg00106.html
http://www.mail-archive.com/perl6-language-objects%40perl.org/msg00112.html

Perl != Python. Perl != Python. Perl != Python... ;-)

-Nate