Re: HELP: Nested include(...)'s take relative paths
| From: | André Cerqueira | Date: | Wed, 11 Feb 2004 02:00:23 +0000 |
| Subject: | Re: HELP: Nested include(...)'s take relative paths | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-177334@lists.php.net to get a copy of this message | ||
If it was a function, parenteses would be mandatory hehe
I prefer no parentheses on include/require/echo/print/..., cant justify it with arguments though, its just the style i chose...
What about:
if (...) { ... } and:
if (...) { ... }I prefer the second, but people find good reasons for each of them... Adam Bregenzer wrote:
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 do most people consider "the right way" ?I always use parens on function calls, I think it is more readable. Also, some syntax highlighters look for it.