Prepare for PHP6!

It’s due out this year. 0.o

If you’re curious on what’s gonna happen with it:

A few nice highlights:

  • register_globals and magic_quote == GONE not “disabled” but GONE. /cheers
  • safe_mode GONE
  • register_log_arrays HTTP_*_VARS are GONE
  • E_STRICT will be within E_ALL

You can read more from the above.

One thing I like about it is the separation of fopen from include in the php.ini. It will mean that, depending on DreamHost’s chosen settings, URL includes can be disabled while leaving URL fopens working.

Simon Jessey
Keystone Websites | si-blog

If I read your post correctly, then curl should not be needed to do read/write files within same domain.

I think PHP is dying… :frowning:

Their approach to backward compatibility truly sucks.

They don’t need a ‘goto’, they need to throw their weight totally behind a rails like framework.

If you are reading and writing within your own domain, cURL isn’t needed anyway. You only need to use cURL for URL access - anything that has http:// basically. With the changes to PHP6, it may be possible to have URL access for opening files; however, you would still not want such a thing for includes because of the security risk.

Simon Jessey
Keystone Websites | si-blog

[quote]I think PHP is dying… :frowning:

Their approach to backward compatibility truly sucks.

They don’t need a ‘goto’, they need to throw their weight totally behind a rails like framework.[/quote]
I couldn’t disagree more. First of all, you cannot really compare Ruby on Rails, and application framework, with PHP, a server-side scripting language. That would be a bit like comparing C++ with Movable Type.

Secondly, Ruby on Rails is slow, partly because it relies on lots of other technologies to work. For example, it has to access database tables in order to generate classes at runtime - very weird.

Finally, PHP is getting better and better. The object support and features introduced with PHP5 have enabled it to compete with Java Server Pages in the enterprise-level world. It doesn’t rely on other technologies to do things, but it can also work with just about anything.

A word about backward compatibility - certain things left over from PHP3 were improved upon in PHP4. Some things left over from PHP4 were deprecated in PHP5. In PHP6, most of the deprecated things will be removed. What is wrong with that? That seems to me to be a sensible upgrade path if you ask me.

Simon Jessey
Keystone Websites | si-blog

Well, I disagree, but I don’t have the energy to discuss it.

I’ve summarized my points from an email I sent a colleage at work some time ago:


Interesting, I guess the info on fopen needs to be more specific as I though fopen was a no go with curl, actually before I figured out how curl kind of works, I thought fopen did not work with curl. But as in the other thread
about fopen, I posted the curl I used, I now know that fopen can be used under certain circumstances. However, when I commented out the curl I received a fopen error.
I’ll play with it more tonight and see if I can elliminate curl as the code is meant for same domain anyways. This I beleive would solve my problem of having 2 blocks of code for read and write, when 1 should beable to do it as a function.

I agree, and they are:
Zend is working with many big names to create a Zend Framework. You can listen to an interview with Andy Gutsman where he talks about PHP6 and the Framework:

Zend is fully aware they need this and they are working on it. In the mean time, I’ve been research current PHP5 frameworks out there, trying to find one worth playing it.

Yep you were right, I was able to make fopen work with out curl. Must have had a bug in the code before. Go figure.