On Wednesday 11 April 2001 17:50, you wrote:
> Thanks to all who suggested using include_once. Maybe it is just me
> (long FORTRAN background), but the very idea of include_once makes me
> nervous, and I don't use it. It violates my sense of acceptable design.
> I would rather design my code such that a file is *really* only
> included once, if that is what is supposed to happen. I *want* PHP to
I'd say *not* using include_once () leads to worse design, because it
means that for every module you have to know (a) where it is included
from and (b) what is included by the files it is included from.
Sounds complicated because it *is* complicated.
It's much better to let each module include_once() everything it depends
on.
--
Christian Reiniger
LGDC Webmaster (http://sunsite.dk/lgdc/)
"These are the people who proudly call themselves "hackers" --
not as the term is now abused by journalists to mean a computer
criminal, but in its true and original sense of an enthusiast,
an artist, a tinkerer, a problem solver, an expert."
- ESR
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
