Bottom line: I always require_once at the top of a file for any files
that I will require. No sense in doing anything else if the required
files aren't there. For conditionally including files include_once()
has always made the most sense to me.
I'm not sure that's the best strategy: since inclu
the file is not even read! The include() method is not only more
efficient but also easier to maintain as you suggest.
The efficiency point is at least debatable -- opening and reading the file
is actually quite an expensive operation, the cost of which may outweigh the
A good point not to be tak
To view the terms under which this email is distributed, please go to
http://disclaimer.leedsmet.ac.uk/email.htm
On 07 January 2005 00:20, Jason Barnett wrote:
> That was what I thought also. However just to add to the
> confusion: I
> think require'd files were evaluated no matter what back
To view the terms under which this email is distributed, please go to
http://disclaimer.leedsmet.ac.uk/email.htm
On 07 January 2005 00:37, Josh Whiting wrote:
> Correction: include() statements are executed at *run time*,
> which means
> that if the case is not executed, the include will not b
4 matches
Mail list logo
