Hello Zeev, Monday, August 7, 2006, 12:02:29 PM, you wrote:
> Marcus, > A few points: > - There's nothing wrong about being lazy, especially as PHP's main > selling point is that it's easy to use (or in other words - also > suitable for people who have better things to do than mess with the language). > - I can assure you that there are a hell of a lot more than 3 people > who are 'lazy' in the PHP arena, and prefer not to be bothered with > what they consider to be noise. Whether they're the majority or the > minority is debatable, but there are definitely many many thousands of them. > - I think it makes perfect sense, from an end user perspective, for > built-in classes to behave slightly differently from userland > classes. Many (most?) users won't make the distinction between a > built-in class and a language feature, it is a language feature as > far as they're concerned, and it makes sense that it will have its > own semantics. > - I don't think we need to tag all of the built-in methods with this > flag, it's absolutely not necessary at the engine level. We should > probably only tag those methods which are callbacks, which would > misbehave if they don't adhere to the same signature as the method > they're overriding. Maybe there's another general case, but for the > most part, most internal methods don't need that flag in my opinion. > And one final note - I think it would greatly help if you realized > that there are many people out there for which the additional OO > features in PHP are not a blessing but some sort of a curse, since it > makes their simple language more complex than it used to be. Nothing > you (or anybody else) is going to say is going to change that, since > it's a fact that today there's a lot more you have to learn and a lot > more concepts you have to be aware of in order to understand PHP > code. Is it worth it? Probably, since it comes with added benefits > - but does it mean we should forget about the price we're paying and > think time and time again about the simplicity > consequences? Absolutely not. Often, that means we'll have to make > compromises, or even not implement certain features at all. Compromises are fine. Not implementing certain stuff is fine. Violating most basic expectations is different. And adding inconsistencies nobody can understand is imo wrong. I just feel very bad with this movement. Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
