Marco Schuster wrote:
On Fri, Aug 6, 2010 at 1:08 AM, Platonides Platonides@gmail.com wrote:
Other patches are not so fine... wfSuppressWarnings();
session_start();
@session_start(); wfRestoreWarnings();
Sure, it was for FusionForge package, but still what error would session_start produce that is not trapped? (I can only make an E_NOTICE or E_WARNING...)
It's enough to break later header(); with "Can't send header information - headers already sent by in foo".
Marco
The point is, both of them are suppressed by wfSuppressWarnings... So what can the @ be suppressed that wfSuppressWarnings may have missed?
Unless the decision to add an @ there predates out own warning supppresion.