Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59404
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zort.net from 96.241.205.2 cause and error)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
In-Reply-To: <CAORXhGLq3ZyShNkqBsPwdabi6SkTqiE00jETiWeXK2T7Lm3gEQ@mail.gmail.com>
Date: Sat, 7 Apr 2012 09:50:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <03FFDCA3-90B2-48CA-B102-7562E0E9CA45@zort.net>
References: <CAORXhGLk8=bJ2TEo0OCzQCacjtGG=ZWYNuXf8Uu8oMNEm2WQ1A@mail.gmail.com> <CAGU04mLu9pniaDw3jAOR7YiX6n3Bk7sMk7T1=4PAvG5QvAZNvw@mail.gmail.com> <CAORXhGLq3ZyShNkqBsPwdabi6SkTqiE00jETiWeXK2T7Lm3gEQ@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] PHP class files without <?php at the top
From: dshadow@zort.net (John Bafford)


On Apr 7, 2012, at 09:39, Tom Boutell wrote:

>> =46rom the viewpoint of someone writing reusable classes, the need to
> start with <?php and reprimand anybody who accidentally puts a newline
> above it is a silly annoyance they don't experience with other tools.
>=20
> That said, you are making valid points, I'm not convinced myself that
> "file extensions" necessarily should or could be determined in every
> context. But it seems the most viable way of addressing the issue - if
> a viable way even exists. Partly I want to convince myself that this
> either can or can't ever be improved, and move on either way (:

That "silly annoyance" doesn't seem to bother anyone who writes command =
line tools, which require the #! line specifying the command interpreter =
to be the first bytes in the file, with no leading white space =
whatsoever. Especially on unix systems (but also on the Mac), the file =
extension does not affirmatively indicate the file type or whether or =
not it can be executed.

Also, from a CLI perspective, you don't want extensions in the names of =
your scripts, because then it causes problems/confusion/extra work if =
you later decide to change the language the script is written in.

-John

--
John Bafford
http://bafford.com/