When was php 5.3 released




















You forgot Honestly, modern PHP used in a correct manner is tolerable Keeping those people out is actually the num. At least magic quotes are now deprecated. Here's looking forward to 6. I've talked to way too many devs who think they are adequate protection against SQL injections.

No, no no. It's a horrible language, but it's built up too much inertia to get rid of it or most of its backward-compatibility disasters.

That's it, easy, let go That's all gonna be alright Somebody call Sadly, I have to agree. A fatal error is issued in such cases. The lack of namespaces in any programming language is a massive car wreck just waiting to happen. I once spent a few days trying to resolve an issue with a web portal application with different components brought together where the issue was caused entirely by a function name collision. The backslash name separator looks awful to me, although I've always found PHP code kind of garish with all the dollar signs and curly braces.

Although it's at least readable compared to some perl I've seen! Looking at the "what's new" list I see the cool new feature of php archives. Seeing that brings up something I've always struggled with in PHP. I guess in the past without namespaces that's probably what most people needed most of the time. And after converting my development wholesale to python with it's inherent namespaces which are really just singleton objects bound to a local name , it seems like PHP's system is a bit convoluted.

Let's say you've been using PHP since about a month after Rasmus released it 15 years back, so you've got a whole lot of code that uses the ereg family of regex functions.

So they've depricated them, and plan to yank them from PHP 6. Is the overhead so terrible? Or do they really think that it will improve our lives if we have to go back through everything and translate eregs to pregs?

Then there's the change in MySQL password formats. Sure, if they include the latest MySQL libraries they have a differe. What are they thinking, when they set out to break this? When 5. And when 6. Given the current state of the economy, this is how you can help keep PHP programmers employed They've been talking about these changes for a long, long time.

If you're still using ereg, or register globals, or magic quotes, or whatever else you want to complain about them changing, then that's your problem. If you have important code laying around that you haven't looked through yet, you might want to pencil that in. There's no reason to have PHP4-only code sitting around these days. Change is almost always painful and scary but you'll be happy for it in the end.

Update the code and be glad they don't stay backwards compatable to every iteration of the language. It's better to clean up and remove the old stuff and continue improving the language. Assuming that people running and maintaining the code are paying any attention, when 6. Nothing is broken. Ereg is moved to the 'official' extension pack called PECL, which you can use for full backwards compatibility. At the same time the community has been warning not to use the ereg functions for the past at least years, if not more, citing worse performance, worse featureset, and the possibility of PCRE replacing it at some point in the future.

Is there somewhere that lists all of the functions that are about to be deprecated? I've used ereg several times in the past few months and am going to have to go and replace those now. It would be nice to avoid the extra work in the future. Theres a list of functions deprecated in PHP 5. I can't find an official list for PHP 6 though. I haven't known it before that. At that time I wrote a comparison, out of anger about PHP being so much used. You might be right about slow machines though.

I don't understand why you make such a big deal about servlets vs jsp, as jsp is just a technology to ease the construction of servlets every jsp gets converted into a servlet They serve same purpose, but they both werent invented for the same purpose.

Out of the two PHP was designed from the ground up to just serve dynamic webpages, and that is its primary purpose. Java on the other hand is designed as an all purpose language. They can fit anywhere that used to take a callback. There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.

Try the CryptoTab Browser. It works like a regular web browser but mines Bitcoin for you while you browse! Works on all devices.

Do you develop on GitHub? You can keep using GitHub but automatically sync your GitHub releases to SourceForge quickly and easily with this tool and take advantage of SourceForge's massive reach. Follow Slashdot on LinkedIn. This release is a major improvement in the 5. X series, which includes a large number of new features and bug fixes.

This discussion has been archived. No new comments can be posted. PHP 5. Full Abbreviated Hidden. More Login. Hooray fileinfo is standard!

Score: 1 , Flamebait. Re: Score: 2 , Funny. Re: Score: 2 , Troll. I use php and do enjoy it but it is ugly. It's unnessary. Re:Hooray fileinfo is standard! Score: 4 , Insightful. Parent Share twitter facebook. Re: Score: 2 , Informative. Re: Score: 2.

Well actually that's what the SPL extension aims to achieve. Re: Score: 3 , Insightful. It's funny how people cling to languages for arbitrary and sometimes downright illogical reasons. It's like each language is cool or acceptable in various online social circles. Re: Score: 3 , Interesting.

Kyosuke writes:. What am I, as a Schemer? A minimalist? A chess player [mit. But seriously, I always saw PHP as one of the prime examples of cargo cult language design. And then the adoption of that strange Java-like OOP system, quite weird for a dyn.

Thank you, you got the gist of my post. Everyone should strive for one. Oh, and you should get bonus points if it is not a politics or religion article. Re: Score: 3 , Funny. Achievement unlocked: [ Post 5 consecutive posts using the Preview button first ].

Re: Score: 2 , Offtopic. Missing Feature. Score: 1. You forgot the most important change of all. They added support for "goto". Re: Score: 1. Yes, adding goto in a language automatically adds multiple levels of awesome.

It doesn't make the code less debug-able at all. Score: 2 , Informative. Score: 5 , Funny. I can't believe they put that in the official manual. Too awesome. Anyway, one excepcional addition to the language is closures [php. Real anonymous functions were missing for a long time on the language, and it is great to have it now. Now it is only a matter of our customers' hosting providers to update their versions of PHP. I didn't said "exception handling", but "error handling", like linux kernel developers [kerneltrap.

Anyway, exceptions in languages like Java which enforces its treatment in compile time are more than just a "goto error handling". It all depends on the language you are using. Score: 4 , Funny. Well, we know where we're going. But we don't know where we've been. Where ever you go, there you are. Re:Would you let it die already?

Score: 5 , Insightful. I think if the functions, calling conventions and naming were regularized. It's true! Score: 2. Years of php programming have danaged my bain to! Say what you will about PHP, but it puts food on my table and a good roof over my head. All users are encouraged to upgrade to this release. For users upgrading from PHP 5.

For a full list of changes in PHP 5. PHP 5. Backwards incompatible change: Methods with the same name as the last element of a namespaced class name will no longer be treated as constructor. This change doesn't affect non-namespaced classes. Fixed a possible information leak because of interruption of XOR operator. Fixed a possible memory corruption because of unexpected call-time pass by refernce and following memory clobbering through callbacks.

Fixed a possible memory corruption in ArrayObject::uasort. Fixed a possible memory corruption in pack. Fixed a possible memory corruption in addcslashes.

Fixed a possible stack exhaustion inside fnmatch.



0コメント

  • 1000 / 1000