Hi! > So we should better begin to see where are the technical bottlenecks > and figure out a way to solve them instead of arguing about whether we > should do it or not. Because we will have to do it, whether we like it > or not.
No, that's exactly WRONG way to do things. We should first know if it's good for PHP and only AFTER we know it's good, we should look for technical bottlenecks. Doing it the wrong way is exactly what got us in situation that everybody recognizes is messy. Because stuff that was technically possible (and some things that only seemed possible if you don't think too hard about them) was done without thinking how it would behave in all the situations and how the rest of the language would work with it. What I do find a bit disturbing is that you think "I know some people that want it" is a good argument to implement any language feature despite quite clear problems that were explained to you - that you think this argument alone is enough to dismiss all these problems as if they didn't exist. You just wave it away and then you are surprised - where this resistance is coming from? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
