[BirdOPrey5]

First- no matter what- even when staff accidentally say we have been suppressing errors since 2002, they mean warnings. PHP warnings. We have been suppressing warnings only. Warnings don't stop execution of the code, warnings don't hurt anything. Most are in fact deprecation warnings that just say "Hey, this code still works but one day you will need to change it."

All forums used in production environments should be setup to suppress warnings and errors to begin with for security reasons- that is good practice. Only development environments should be showing warnings and errors.

Our competitors also suppress warnings in their software in normal modes. It is common practice is all PHP software.

4.2.2 was the first time in a long time many of the long-standing issues were addressed. Everyone who is saying "how come you didn't fix it instead of hide it" well 4.2.2 (and 4.2.3 now in beta) are the result of actually fixing the issues rather than hiding them.