RE: Re[2]: [PHP] HELP: Nested include(...)'s take relative paths not intuitively

2004-02-11 Thread Ford, Mike [LSS]
On 11 February 2004 00:38, Adam Bregenzer contributed these pearls of wisdom: On Tue, 2004-02-10 at 19:06, Richard Davey wrote: This is slightly off-topic, but related to the include() function. What is the given standard regarding when you should or shouldn't use braces on a function.

Re: Re[2]: [PHP] HELP: Nested include(...)'s take relative paths not intuitively

2004-02-11 Thread John W. Holmes
From: Ford, Mike [LSS] [EMAIL PROTECTED] Mind you, there are exceptions: exit(), for example, is a language construct but requires the parens (at least, that's what the fine manual appears to say, and I've not tested it without!). Only if you want to pass an exit value, i.e. exit(101);

Re[2]: [PHP] HELP: Nested include(...)'s take relative paths not intuitively

2004-02-10 Thread Richard Davey
Hello John, Tuesday, February 10, 2004, 8:20:50 PM, you wrote: JWH include($_CONF['path'] . '/test.php'); This is slightly off-topic, but related to the include() function. What is the given standard regarding when you should or shouldn't use braces on a function. For example: include

RE: Re[2]: [PHP] HELP: Nested include(...)'s take relative paths not intuitively

2004-02-10 Thread Martin Towell
Hello John, Tuesday, February 10, 2004, 8:20:50 PM, you wrote: JWH include($_CONF['path'] . '/test.php'); This is slightly off-topic, but related to the include() function. What is the given standard regarding when you should or shouldn't use braces on a function. For example:

Re: Re[2]: [PHP] HELP: Nested include(...)'s take relative paths not intuitively

2004-02-10 Thread Adam Bregenzer
On Tue, 2004-02-10 at 19:06, Richard Davey wrote: This is slightly off-topic, but related to the include() function. What is the given standard regarding when you should or shouldn't use braces on a function. [snip] Both work just fine. The manual includes examples of both methods. So which