Hi! On 8/1/11 3:30 PM, Hannes Landeholm wrote:
lists or write RFC's or learn C or jump trough endless hoops in a process designed so that the core development team can ignore the community more democratically. The users that just suck it up and design their applications or frameworks poorly instead because they don't have time.
I notice some tone of hostility here. Please understand that while your problem seems to you the most important thing missing in the language, and maybe for you it is, PHP has millions of users, which need stable and predictable environment. Which means relying on your or my personal opinion about some matter is a dangerous thing as it can influence how millions of people work. This is why we tend to be careful with adding stuff to the language, especially stuff that has potential long-term consequences, most of which we don't even know about until this thing has been tried in the field. Also, it is very hard to substantially change stuff in the core once it's there as we have to preserve BC.
This is why we tend to recommend to try the code outside the core if possible before taking it in.
I'm not sure how to respond to that. "The more I look at it" does not parse as an actual argument of anything in my head. Be more specific. I strongly disagree that Weak References should be buried in a PECL
You seem to regard PECL as some kind of place where code goes to die. This is not so. Of course, some PECL extensions do wither and die of neglect, but others work just fine and have large user base - such as memcache support, apc, etc. Recommendation of PECL is not a punishment or disregard for your ideas or code - it is a recognition of the fact that not every new idea should immediately be implemented in the core.
Also I'm not sure what you expect when you say that it "reached more maturity". To what end? A feature doesn't really get much more well defined and simple than this. It's like the whole "it's a single class
If you think all proposals are more complex than this, you are obviously wrong. Most of recently added things into 5.4 in fact are conceptually simpler.
simplicity. Unfortunately I don't have time to wait for years even if many of you guys do. If I did I wouldn't have bothered writing the RFC or writing in this mailing list. You guys should look into this new rapid release cycle thing. It's the next iteration of software development.
Rapid release cycle doesn't mean that we immediately put into the release everything that was proposed up to the last second when it's supposed to be released. If you need a solution for your use cases, I don't see how PECL extension wouldn't be fine. If you're looking for something which would run on shared hosting, many shared hosts wouldn't support 5.4 for a long time even after it's released. Also, I am sure there are ways to implement the same ideas without this specific class (indirection can be one idea that may work - it's in fact what PHP does internally with objects). It may not be the best way, but I think it's doable.
-- 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
