Quote:
|
Originally Posted by Easywebdev
I would like to see the developers bite the bullet on v6 and forget backward compatability and implement everything they would like to in 6 and release it as a seperate language.
|
Fully agree. My Danish hoster has 5.14 installed. PHP 5.2.0 was released Nov 02. A good hoster should
- Offer an option to use the last and an older stable version.
- The last version should be available at least for experimental purposes no later than a month after it was launched.
To go back to topic, the future may be uncertain for session variables. The best solution is therefore to write a session class that we wrote about in
the other WPW session thread menitioned above.
That is the good thing about classes. You only update the class API and you do not need to rewrite your older classes.
A good OO design make your code more forward compatible.
I like this cite from the preface to volume II by Harry Fuecks.
"If I had one goal in mind with writing the PHP Anthololgy Object Oriented PHP solutions, it was to demonstrate just how easy it is to create intricate and powerful Web applications with the object oriented approach. In many cases, the more common procedural approach would result in unmanageable and bug-ridden "spaghetti code.""
More and more pople understand that. The drinks machine (automaton) that has its inner workings ("API") changed functions just as before. The user does not see the change and he need not worry about it. He hists the same buttons. If the designer wants to add new drinks to the automaton, he extends the API (class inheritance). The user only sees some new buttons (methods.) The inner working of the drinks machine is encapsulated. OOP in a nutshell.
Final recommendation: Write / import a session class, and you will not loose your hair so fast.