Re: HELP: Nested include(...)'s take relative paths

On Tue, 2004-02-10 at 21:00, André Cerqueira wrote: > 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... I'm anal about code formatting. I always use parens with no space before a function call, put a space before parens for builtin words (if, while, etc), don't indent case phrases, move multiple arguments that go over 80 characters to their own lines, and always use the former of the above methods. Of course, if I am modifying someone else's code I *always* use the coding standards already in place. The most important thing is to be consistent. Everybody has their own preference about how using different coding styles increases or decreases readability, however I think what really improves readability is commenting, not coding style. -- Adam Bregenzer adam@bregenzer.net http://adam.bregenzer.net/