My stance has always been that suppressing the warning is fine if the file is auxiliary. But i would suggest an "if file_exists" condition
-----Original Message----- From: Wade Preston Shearer <[email protected]> Sent: Thursday, March 26, 2009 11:07 PM To: Utah PHP Users Group Discuss <[email protected]> Subject: [UPHPU] @include_once bad? Is there anything improper about using @include_once() for files that may not exist (suppressing the error)? Would it be more proper to remove the @ and wrap the include in an is_readable() to verify that the file exists and is readable first? _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
