ole wrote:
Case sensitive functions
Which problem would be solved by making function names case-sensitive?
Where's the advantage of having different results for a doX and DoX call?
How long would it take for the average developer to become aware of this? Even nowadays i still see: 'Help my variables have disappeared (register_globals)' posts...
Still convinced that we need case-sensitivity?
ole wrote:
Properly standardized functionNames(), arguments and return types
Cleaner global namespace
Imho, the PHP API was not designed, it just grew into what it's today. On the other hand, for most PHP function calls there seems to be a rationale behind the arguments and their order, so i don't really see how they could make it any easier...
A decent editor/ide will remind you to the function signature and show hints for the arguments..
By cleaning it up (or trying to do so) you're going to break backwards compatibility.. For what?
What i don't like is that there is a trend towards doubling the functions by offering both a Class::Method and a class_method function that do the same. (Note to myself: Is that consistent with what i said about DoX and doX?)
ole wrote:
Built-in Optimizer
This is a suggestion i do agree with. Probably because it doesn't influence the 'programmer interface with php'.
ole wrote:
Out dated function sets replaced with more comprehensive classes
Which function sets are you referring to? And with what would you replace them?
ole wrote:
Bundled with Zend Framework
I don't see why this would be a good thing considering the current status of ZF.
If we consider the bundling of php with pear we already know that it doesn't work
ole wrote:
Manatory OO based development (maybe objective input and output streams for example)
And the advantage would be? (Not interested in yet another my methdology is better than yours discussion)
ole wrote:
Drop double-quote string syntax?
I'm assuming you're referring to variable variables. What is wrong with it that you would remove the functionality?
ole wrote:
Drop variable dollar symbol syntax?
Why drop the syntax? With what would you replace it?
The only reason i can imagine would be aesthetics, and that doesn't seem like a good criterium.
ole wrote:
Separating PHP out into two versions would also have psycological implications. For example there would be forums for PHP Classic and forums for PHP Pro and a good deal of the users of these forums would stay on one of the other and created separate environments.
In essence, there would be a good and a bad version... Why on earth would we need a bad version?
I do know very well that PHP5 has functionality that PHP4 doesn't have. But when i develop an application for a specific target i'll have to live with the constraints of that target. Apparently the constraints that PHP4 has don't stop people from creating solutions for their problems. It's a matter of choosing the right tool for the right job.
ole wrote:
Anyway that's my piece. I'm not saying this is a good idea but I'm interested in peoples opinions on this and also people would like to see put into PHP to aid more serious developers.
How would you define 'more serious developers'?
And what would their needs be?
Why would we have to change PHP to suit their needs?
Since they're more serious developers, can't they make it theirselves instead of harassing us with it?
Personally i do see a need for:
- namespaces.. Eg: Which framework doesn't have a Date class?
- unicode
- since the default content-type for php is text/html i would expect the default output for echo/print calls to use htmlentities. This way it becomes harder for average php programmers to shoot themselves in the foot. On the other hand, magic_quotes hasn't helped either.. PHP is doomed.. It's relatively easy to use, so you will see lots of code written by beginners.. Just like you could see a lot of Visual-Basic code... And yes, in the end PHP will get the same reputation as Visual-Basic by so-called 'serious developers'.