Hi Harald, >> >> I can see your point, but I think we should drop this "feature" not to >> let developers have N ways of doing the same things: > > why should ANYTHING be dropped affection backward compatibility? > >> if you declare a method as static, you should be able to only call it >> with a static call, not hrough an object. > > that is a opinion, but not enough to damage BC
I think this should be the subject to talk about, whether or not this is something we accept to break retro-compatibility for. > >> PHP usually lets you do the same thing in a few ways, and that's a bit >> frustrating > > there are so naby different woman and cars out there and that's a > bit frustrating - you know what i mean? definitely not The main point is to force developers to follow some practices, like when you type-hint a core method of your framework (just an example here) others can extend, instead, for example, of doing class-oriented programming. > >> because we should force some kind of best practices for >> the language: not .advise, but *force* > > maybe you are using the wrong language if this is your opinion? > nobody says "stop selling guns because somebody can shoot in his foot" That's why in lots of countries you should demonstrate to the competent authority that you are able to manage a gun in order to get it :) > > peacefully talking, no need to be such aggressive -- Nadalin Alessandro www.odino.org www.twitter.com/_odino_ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
