Re: RFC 161 (v4) Everything in Perl becomes an object.

>>>>> "Michael" == Michael Fowler <[email protected]> writes:

Michael> If $str = "foo" and m/foo/ are somehow magical objects,
Michael> that's fine, as long as it doesn't impact my not wanting to
Michael> use them as objects.  That'd be some feat, but if you can
Michael> manage it, more power to you.  Everytime I see the title
Michael> "Everything in Perl becomes an object" I groan and have to
Michael> wonder exactly what the point is.  OO is a neat tool,
Michael> sometimes, but Perl has done rather well without having
Michael> objects -everywhere-, and I like my Perl pretty much the way
Michael> it is.

Yes, this is what I was getting at.  Python suffers from the
"everything's an object" (or so the press kit says) paradigm, because
they didn't spend enough time optimizing for *common* things.  As I
like to tell people, in Python, "everything is equally difficult".

So, I'd be happy to make everything an object under three conditions:

1) it doesn't interfere with *optimized* language constructs for
the most common tasks

2) it isn't being put in just to satisfy some theory that making
everything an object will make everything easier

3) it doesn't slow things down for those of us who want to use the
optimized interfaces and not worry about objects until we get to
500-line programs

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<[email protected]> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!