> I have to say that no matter how much a luv my OOP, turning every > built-in type into an Object is just a Bad Idea... > > It's a form of bloat on RAM and CPU with minimal added value, imho. > > No matter which way you twist this pretzel: > > -1
Re-read what I had written. I never said to turn every built-in type into an object. In fact, what I was talking about was keeping and preserving the base types as-is. All that I was proposing was adding the ability to cast from and to the primitives. That way you could silently convert back and forth as needed (transparently when possible). So what it sounds like you're -1ing to, is not actually what was proposed... I'm starting to work on a patch for this as a proof of concept... Anthony On Mon, Feb 27, 2012 at 10:08 AM, Richard Lynch <c...@l-i-e.com> wrote: > On Sun, February 26, 2012 9:48 am, Anthony Ferrara wrote: > > I have to say that no matter how much a luv my OOP, turning every > built-in type into an Object is just a Bad Idea... > > It's a form of bloat on RAM and CPU with minimal added value, imho. > > No matter which way you twist this pretzel: > > -1 > > -- > brain cancer update: > http://richardlynch.blogspot.com/search/label/brain%20tumor > Donate: > https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
