Check the new version here

Popular channels

Upcoming changes in PHP 6.0

The PHP world is really excited about the upcoming release of PHP 6.0. Amongst all the uncertainties in any new release, PHP 6.0 seems to be getting rid of three of the earlier troublesome features: register_globals, magic_quotes_gpc and safe_mode. The first was a big security hole, the second messed with the data and made changing environments quite difficult, while the third was usually misread, and provided a false sense of security. There's also quite a lot of work scheduled to do with Unicode. Read more for some of the changes:

* The register_globals, safe_mode and various quotes options will be removed.
* The ereg extension is removed, while the XMLReader, XMLWriter and Fileinfo extensions are added to the core, and by default are on.
* Another addition I find particularly exciting is that APC (Alternative PHP Cache) will be added to the core, though will be off by default. APC can provide serious performance benefits.
* All E_STRICT messages will be merged into E_ALL, another positive change that will encourage good programming practice.
* ASP style <% tags will no longer be supported.
* Addition of new 64-bit integers. The current integer type remains as is, 32 or 64-bit dependent on the platform.
* Use of foreach with multi-dimensional arrays, for example foreach($array as $k => list($a, $b)).
* A new switch in php.ini will allow you to disable Unicode semantics (by default they will be on).
* There will also be various string improvements related to Unicode.
* The microtime() function will return the full floating point number, rather than microseconds unix_timestamp, as at present, probably making the function more readily useful.
* The {} notation for string indexes will no longer be supported, while the [] version will get added to substr() and array_slice() functionality.
* FastCGI will always be enabled for the CGI SAPI, and will not allow it to be disabled.
* The ancient HTTP_*_VARS globals will no longer be supported.
* var will alias public. var was permitted with PHP4 classes, but in PHP 5 this raised a warning. In PHP 6 var will simply be an alias for public, so no warning is necessary.
* The ze1 compatibility mode, which tried to retain PHP 4 behavior but had some bugs, will be removed.
* Dynamic functions will no longer be permitted, to be called with static syntax.


There's a lot to be determined, namespaces being one of the more important, but it would take a while before we see the final product, but everyone’s excited the way it seems to be heading, and the progress that is being made.

Fuente: http://www.phphacks.com/content/view/49/33/
0
10
0
10Comments
      lenny321

      disculpa por no molestarme en leer el post ya se que php es una mierda, hasta cypher
      lo sabe (el funcionamiento de Taringa lo confirma). Aguante JSP!!!!!!!!!!!!!!!!

      0
      andres

      [quote]* var will alias public. var was permitted with PHP4 classes, but in PHP 5
      this raised a warning. In PHP 6 var will simply be an alias for public, so no warning
      is necessary.Son peor que la gata flora!

      [quote]There's a lot to be determined, namespaces being one of the more important,
      but it would take a while before we see the final product, but everyone’s excited the
      way it seems to be heading, and the progress that is being made. Esta es la
      mejora más relevante. Realmente es muy complicado trabajar en grandes proyectos OOP,
      cuando no se cuenta con la abstraccion de "paquete".

      lorca, el solo saber que python delimita su scope por indentacion, me hace dudar de
      la claridad, y flexibilidad sintáctica del lenguaje.

      0
      nga

      hijo de pooh volve a tu casa

      0
      soto

      foro de nerds.

      0
      lorca

      andres, en que te besas para decir que eligirias ruby?

      por rails?
      nah... ruby es lento y para chinos

      python es un lenguaje de sript hasta ahi, en realidad python se compila, lo podes usar como script tambien... ruby es para losers, ahora todo dicen "ruby" por ruby on rails, pero ruby como lenguaje (por lo menos la suntaxis es horrible) python es elegante

      0
      andres

      La verdad es que los lenguajes de script para hacer aplicaciones son una verdadera
      poronga. Si tengo que elegir un lenguaje de script, elijo Ruby, pero igual, sólo lo
      utilizaría para administración de sistemas. Para hacer una aplicación grande, hay que
      elegir una plataforma, y obviamente, LA plataforma se llama Java.

      0
      lorca

      che mucha paja

      0
      lorca

      home666, si, es por todo lo que dijistes,
      la curva de aprendizaje de python es mejor todavia, y ademas es un lenguaje totalmente orientado a
      objetos

      yo antes programaba en php, osea laburaba y todo con php, pero cuando conoci python me cambio
      todo, mas simple, mas potente, mas elegante, y todo...

      php es respetable por la cantidad de adeptos, al igual que VB, el lenguaje en si es una mierda pero es
      respetable por eso...

      instalar mod_python es mas facil que instalar mod_php

      0
      home666

      ¿Será por que es el que tiene mejor curva de aprendizaje? ¿Será por que miles de
      hosting ofrecen por defecto apache/php/mysql a precios accesibles?

      aguante python carajo!

      Aguante! =P

      0
      lorca

      todo el mundo programa en php, la verdad a mi personalmente no me gusta, pero bueno, lo respeto
      por la cantidad de paginas en php que hay...

      aguante python carajo!

      0