An Early Look At What's Coming In PHP V6
IndioMan writes "In this article, learn about the new PHP V6 features in detail. Learn how it is easier to use, more secure, and more suitable for internationalization. New PHP V6 features include improved support for Unicode, clean-up of several functions, improved extensions, engine additions, changes to OO functions, and PHP additions."
Update — May 7th at 16:47 GMT by SS: IBM seems to have removed the article linked in the summary. Here's a different yet related article about the future of PHP, but it's a year old.
without wanting to be overly sarcastic..
What features are they gonne break this time?
I am definitely no PHP expert so perhaps I am wrong but it seems that much of what is being changed is backtracking due to bad language decisions from the beginning. Sadly I think PHP developers with legacy code are going to be paying the price for several versions to come.
Play me online? Well you know that I'll beat you. If I ever meet you I'll "/sbin/shutdown -h now" you. -Weird Al, kinda.
are these ass clowns still planning on using \ for namespaces?
Do you even lift?
These aren't the 'roids you're looking for.
Given that PHP 6 was "rumored" to be out at least a year ago. I can't decide if the title "An Early Look" is meant to be ironic, or is just a sad indicator of progress.
Despite that, I would say that three things have recently happened demonstrating the improvement in quality of PHP:
I would say that (1) and (2) easily are more important for the language than is (3). PHP 5.3's improvements should be a huge change: Namespaces (I know there's a huge amount of hate for this implementation: get over it. It's going to be very useful), Closures / Lambda Functions, and Late Static Bindings in particular make it hard to wait so long for PHP 5.3.
So, stop talking about PHP 6! Lets get PHP 5.3 out.
clean-up of several functions
Does that include safe_quote_string_this_time_i_really_freaking_mean_it, or do_foo(needle, haystack) and foo_do(haystack, needle)? At least it gets namespaces after all this time, even if they're almost deliberately ugly.
Dewey, what part of this looks like authorities should be involved?
So let's say you've got a global variable, $n
And let's say you're using it in a module, Foo
And because scattering global variables everywhere is a stupid idea that will lead to much pain, let's say you've decided to use namespaces in PHP6.
Now, in your main script, let's say you happen to be using a variable $Foo, for no particular reason.
What does this do?
<?php
echo "Hello $Foo\n";
?>
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
One thing I hope PHP would have is GUI stuff for both Windows and Linux. Its a great language for everything, and I use it constantly for scripts and other stuff. I've even written ircbots and servers with it, and they all work great and are nice to work with.
However the GUI design with the existing tools is just pain in the ass, and it doesnt offer a good way to turn your code into machine code.
I do understand that theres programming languages like c/c++ and delphi and several others, but from all of those php is the nicest to use, even for non-webpages stuff.
I dont think it would be that hard to implement such, given theres people to do it and understand how PHP can be greatly used for non-webserver stuff aswell. Or is there something against it that I havent thought of?
One of these things just doesn't belong
python:
myArray.append(myvalue)
ruby:
myArray.push(myvalue)
objective-c:
[myArray addObject: myvalue]
smalltalk:
myArray add: myvalue
PHP:
array_push($myarray, $myvalue)
In the finest tradition of PHP, they made Unicode behaviour dependent on a setting. Have these people learnt nothing from the past? magic_quotes anyone? Bleh. All languages have their warts, but the amount of bad design decisions in this one is just staggering.
Ubiquity is a pretty compelling feature.
I mean, BeOS is pretty bitchin', but I'm not spending any of my time on developing applications for it.
Potato chips are a by-yourself food.
Too bad Slashdot still wonâ(TM)t.
I mean, won't.
Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
Because it's syntactically similar to C. It's remarkably close to what C++ should have been---C with classes, integrated hashes, variable-length arrays, and usable string manipulation. Thus, for long-time C programmers, it's a very natural language to pick.
Check out my sci-fi/humor trilogy at PatriotsBooks.
That's so cliché.
PHP: its like fast food..
You know its bad for you...
You feel like crap after eating it...
But damnit, its right there, oh so conveniently located on the way to work, and sometimes a greasy cheeseburger just hits the spot, even though you know you'll pay for it later in heartburn and much later in high cholesterol and love handles, even though right now its really cheap on the wallet.
Its a guilty pleasure.
And while you're sucking down that greaseball burger, you see the local soup and salad restaraunt and think "next time, I'll eat right.."
But come the next day and you see that taco joint and..
-- Senior Software Engineer, Attorney appearance services, locallawyerapp.com.
here's the correct one: http://www.ibm.com/developerworks/opensource/library/os-php-future/