View Single Post
Old 03-03-2023, 12:45 PM  
Klen
 
Klen's Avatar
 
Industry Role:
Join Date: Aug 2006
Location: Little Vienna
Posts: 32,235
Quote:
Originally Posted by k0nr4d View Post
It really depends on how you coded. There are behavioral changes that break code, needlessly. The biggest thing that pisses me off specifically, is that you can no longer do:

if($var) { ... }

Before, if $var was not set at all it was just false and didn't enter that. Worked for years and years. Now, that would throw a fatal error. You now have to do:

if(isset($var) && $var == true) { ... }

So it introduces alot of fatal errors where it wouldn't throw them before.
You mean if you have unset variable it goes fatal error ? I think that was already before, tho just throwing warning, not fatal error. But that is normal with every php upgrade, always doing shit like that. For example, when php 5.3 was issue, if your script did not had set time zone, you would get fatal error.
And it's not just PHP, MYSQL latest version now require to always insert something otherwise query does not pass, meaning it cannot be empty.
Klen is offline   Share thread on Digg Share thread on Twitter Share thread on Reddit Share thread on Facebook Reply With Quote