Re: good practice
| From: | Philip J. Newman | Date: | Fri, 15 Feb 2002 04:04:49 +0000 |
| Subject: | Re: good practice | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-84861@lists.php.net to get a copy of this message | ||
WHo really cares, if it works it don't matter what they call it.
----- Original Message -----
From: "Peter J. Schoenster" <php@errorcode.com>
To: <php-general@lists.php.net>
Sent: Friday, February 15, 2002 5:36 PM
Subject: Re: [PHP] good practice
> On 14 Feb 2002, at 16:40, Michael Kimsal wrote:
>
> > On that same topic, *why* do people name files with both .inc and
> > .php?
> > Your .inc file has PHP code in it, right? Why not just call it .php
> > and
> > spare the server reconfiguration. If knowing which files are
> > "include" files (long time since I've made that distinction!) just
> > prepend them with inc_ or put them all in an includes/ directory.
>
> Heck, I've seen inc,cls,html,php3,php4
>
> Whoever started this thread was on the right track. Where are the
> global coding conventions for PHP?
>
>
> http://www.linuxdoc.org/HOWTO/PHP-HOWTO-12.html
> http://utvikler.start.no/code/php_coding_standard.html
>
> Any othes out there?
>
> I know I have my pet peeves about Perl but Perl, as hard as it may
> seem, appears more rigid than PHP :)
>
> Peter
> http://www.readbrazil.com/
> Answering Your Questions About Brazil
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
>