[UPHPU] @include_once bad?

thinbegin thinbegin at gmail.com
Fri Mar 27 00:41:54 MDT 2009


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 <wadeshearer.lists at me.com>
Sent: Thursday, March 26, 2009 11:07 PM
To: Utah PHP Users Group Discuss <uphpu at uphpu.org>
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?



More information about the UPHPU mailing list