LookAhead: PHP5 Feature Set
Moderator: General Moderators
LookAhead: PHP5 Feature Set
Just wanted to get your opinion on the upcoming features for PHP5, and to see which ones you like the best. Vote away, and feel free to discuss.
To get the details on each feature, you can read it here: http://www.phpvolcano.com/articles/php5/index.php
Note: Namespaces are NOT being implemented in PHP5 as of right now.
To get the details on each feature, you can read it here: http://www.phpvolcano.com/articles/php5/index.php
Note: Namespaces are NOT being implemented in PHP5 as of right now.
-
Cruzado_Mainfrm
- Forum Contributor
- Posts: 346
- Joined: Sun Jun 15, 2003 11:22 pm
- Location: Miami, FL
ok jason, here is my opinion of how the try/catch should be:
try {
//anything can result false or true
}
except {
//if an error in the try above happened, then this happens too
}
finally {
//i take the name from Delphi(object pascal), and this
//will only happen if there were no errors in try or warnings etc etc
}
hopes the best
try {
//anything can result false or true
}
except {
//if an error in the try above happened, then this happens too
}
finally {
//i take the name from Delphi(object pascal), and this
//will only happen if there were no errors in try or warnings etc etc
}
hopes the best
- Sevengraff
- Forum Contributor
- Posts: 232
- Joined: Thu Apr 25, 2002 9:34 pm
- Location: California USA
- Contact:
- trollll
- Forum Contributor
- Posts: 181
- Joined: Tue Jun 10, 2003 11:56 pm
- Location: Round Rock, TX
- Contact:
I don't know, for me private/public and everything just seem like part of the picture as far as OO usefulness goes. Definitely a welcome aspect, but I really hope that PHP starts going in the direction of interpreted java. Let it work well from installation to installation and let it f**king work as an OOP language... I could use some good implementations of "try { } catch { }" as well as interfaces. One day we'll get to multiple inheritance, we just need to give them time to sort it out. And if you can't give them time, code it yourself and stop complaining.
PHP 5 by default now without MySQL?
:? Does someone know something more about this topic? Or is this ment just for the beta cycle?
Mmm... I just like PHP5 in general. I hope they take thier time on this release and get everything working great before releasing it... this beta almost seems a little soon in my opinion, but it is very welcome.
The fact that they are advancing the OOP interface so much is just awesome. I think it's deffinately a step in the right direction.
One thing that's been bugging me tho is all the people that think PHP should look like Java... I disagree with this because PHP needs to become PHP, not a Java look alike. Yes, it could use better OOP still and other things... but it needs to do it's own thing and go it's own direction. Not to start another holy war or anything, but these are just my thoughts.
One thing that's been bugging me tho is all the people that think PHP should look like Java... I disagree with this because PHP needs to become PHP, not a Java look alike. Yes, it could use better OOP still and other things... but it needs to do it's own thing and go it's own direction. Not to start another holy war or anything, but these are just my thoughts.
-
electronerd
- Forum Newbie
- Posts: 1
- Joined: Sun Jul 06, 2003 10:01 pm
There is a problem here. Automatic pass-by-reference is a BAD THING(tm) for old scripts that rely on the old system. Not to mention that this is the exact opposite behavior I have seen in every other language I have seen. I don't see the problem with having to specify pass-by-reference. n00bs should just have to learn to deal with it. Not to mention, what do you do if you want to pass by value?
All the new OOP features are truely great. It's important that all programming languages including PHP, have a common OOP Look&Feel in the future. It might look as if PHP5 is copying Java, but there's nothing wrong in learning from a solid OOP language.
* passing by Reference (by default) is great!
* Exception handling is a must!
* multiple inheritance might cause more bad than good..(interfaces will solve the problem)
btw there aren't any articles/tutorials on using DOM/XML & SQLite with PHP5.. at least a simple intro would greatly help.
* I'm actually in the process of developing a rapid web development framework for PHP5 (like enhydra for Java) and could realy use some help with the DOM/XML changes in PHP5.
thx.
* passing by Reference (by default) is great!
* Exception handling is a must!
* multiple inheritance might cause more bad than good..(interfaces will solve the problem)
btw there aren't any articles/tutorials on using DOM/XML & SQLite with PHP5.. at least a simple intro would greatly help.
* I'm actually in the process of developing a rapid web development framework for PHP5 (like enhydra for Java) and could realy use some help with the DOM/XML changes in PHP5.
thx.
1. I don't think there are many old scripts that rely on the old system. Anyone that was aware of the old system wouldn't have used it. Generally, BC is being kept.electronerd wrote:There is a problem here. Automatic pass-by-reference is a BAD THING(tm) for old scripts that rely on the old system. Not to mention that this is the exact opposite behavior I have seen in every other language I have seen. I don't see the problem with having to specify pass-by-reference. n00bs should just have to learn to deal with it. Not to mention, what do you do if you want to pass by value?
2. You must not have worked with many other languages if you think PHP is the first to treat objects differently then a normal variable.
3. There ARE problems with having to specify pbf in PHP. The current implementation prevents you from coding certain basic OO functionality. This is not acceptable. Simply put, the current implementation is done poorly (as has been admitted by those who implemented it).
4. n00bs aren't the one's that have the problem. It's the people who are more experienced who are hitting brick walls in PHP.
5. __clone() exists for that very reason.
You may feel your reasons are justified, however, not doing something because of 0.0001% of the users out there need to use functionality that is broken isn't a good reason to not change it. If you really need to pbv as the default mechanism, don't upgrade.
It'll be nice to have private/protected modifiers for variables and functions.
When reading this forum and other forums I see a lot of people being concerned about PHP evolving into a Java look alike. I don't see the problem. Java is a great language for OO programming. I like the way Java handles things. If PHP can adopt the OO of Java, the speed(and textformatting) of Perl, and still keep its simple syntax, I almost wouldn't consider using Java(JSP) on my projects. (And I love programming Java).
PHP has a great future as an object oriented language.
When reading this forum and other forums I see a lot of people being concerned about PHP evolving into a Java look alike. I don't see the problem. Java is a great language for OO programming. I like the way Java handles things. If PHP can adopt the OO of Java, the speed(and textformatting) of Perl, and still keep its simple syntax, I almost wouldn't consider using Java(JSP) on my projects. (And I love programming Java).
PHP has a great future as an object oriented language.