Anyone notice? (pun intended)

I removed the restriction about notices and warnings. Everyone hated it and complained so much that I got rid of it...

no! i didn't hate them!

they make everyone make nice and clean code...

every beginner can learn with warnings on!

if everione written code that doesn't produce warnings, php team wouldn't change register_globals to off!

i didn't hate them too.

i always test with notices and warnings turned on, i think the resulting code is more stable.

it is not difficult to avoid notices and warnings, it only requires some easy thoughts. in other programming languages you'd have to care about that anyway( for example variable - initialization )

Personally I can't see the reason to complain about scripts not generating notices and warnings. If you write code for a real project, there's got to be no warnings or notices.

I wouldn't mind having that "restriction" back.

As I see it it's up to the developer now. If you like notices (as do I), turn them on, if not, your problem?

Many bugs can be caught using notices, but if people prefer not to use them, it's their choice.

Just an example why I hate notices.
When you handle POST requests in a web application and there are hundreds of optional input items, you don't really want to check if each of them has things entered with isset()... 'cause... you'd have hundreds of isset() statements! You'd just want them to evaluate to false instead of having a notice telling you that it's undefined and php is assuming it's false.

and why did we ask questions to zeev?

look at his answer to one question where he mentions notices

Yea... I wouldn't say the code I mentioned above "higher quality". Having hundreds of useless lines just sitting there is inefficient.

Help writing the core is one thing. Actually writing applications for it is another.

u can add @ for such purposes...

but, if you have hundreds of input items, and u manualy add them in you code, maybe there is something wrong with your code?