public static function notice($message){

		// Remove all superfluous white-spaces for increased readability

		$message = preg_replace('/\s+/', ' ', $message);

		static::writeLogLine('Notices.log', $message);

		trigger_error($message, E_USER_NOTICE);
	}
public static function notice($message){

		// Remove all superfluous white-spaces for increased readability

		$message = preg_replace('/\s+/', ' ', $message);

		static::writeLogLine('Notices.log', $message);

		trigger_error($message, E_USER_NOTICE);
	}
public static function notice ( $ message ) { // Remove all superfluous white-spaces for increased readability $ message = preg_replace ( '/\s+/' , ' ' , $ message ) ; static :: writeLogLine ( 'Notices.log' , $ message ) ; trigger_error ( $ message , E_USER_NOTICE ) ; }
Trigger an "assert-type" notice.

<p>In some situation we want to evaluate an assertion, but know on beforehand
the expression will evaluate to <em>false</em>. This happens, for example,
in the "default" case of a switch statement. In those situation we (ab)use
the assertion as a "stricter than FireLogger" logging mechanism.</p>

<p>In those situation it is prudent to trigger an E_USER_NOTICE instead of
an assertion, as this better fulfills the goal of strict (but not fatal)
logging. This method is purely intended as some syntactic "sugar" around the
regular call to {@link trigger_error()}. This is in anticipation of the fact
that in the future we might find an even better way to handle these
situations.</p>

<p>When the self::enableNoticeLogLine function has been called with a log
file, this function will write a log line. This needs to happen before
calling trigger_error, because on live environments the E_USER_NOTICE
errors are ignored.</p>

<p>Under normal circumstances (c.q. when used in conjunction with the other
functions offered in {@link ExceptionHandler.php}) this method will generate
a PHPErrorException.</p>

@param $message
@return void
Trigger an assert - type notice .