Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59503
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.161.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F82E13A.7010209@developersdesk.com>
References: <CAORXhGJwmbjw3Zze3+-oFA2Mb_Z-2owVESraNMMs57RzjRRMbA@mail.gmail.com>
	<CAORXhG+owfXp2RrBLhRXKgHoYdza7Vj1V21N_AhCyFkAvfLgkA@mail.gmail.com>
	<4F82D57F.8020101@gmail.com>
	<4F82E13A.7010209@developersdesk.com>
Date: Mon, 9 Apr 2012 09:40:07 -0400
Message-ID: <CAORXhG+Dn9j2QRbnGL=Mj41C6ZHw0RsBqRFDbFjx_bbNX4yC5g@mail.gmail.com>
To: Rick WIdmer <vchkpw@developersdesk.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: RFC: source files without opening tag
From: tom@punkave.com (Tom Boutell)

On Mon, Apr 9, 2012 at 9:16 AM, Rick WIdmer <vchkpw@developersdesk.com> wro=
te:
>
> Option 1: Introduce require_path
>
> I think require_code is a better name. =A0Parm 1 isn't a path, it is a fi=
le,
> so require_path seems wrong to me.

Yeah, you're not the first to say this. require_file and require_code
have both been suggested. I'm fine with either really.

> I'd prefer a 'start in code mode' optional second parameter to
> include[_once] and require[_once].

That would be fine as far as my goals here go, but I'm concerned that
we'll just repeat this discussion if any other options for requiring
things come into being (:

> Option 2: Filename Convention
>
> The PHP engine should not know or care what the file extension is. =A0I w=
on't
> object if you can convince autoloader authors to follow the .phpc
> convention. =A0Personally, once I can count on this feature, every file I
> include/require will probably be written starting in code mode and using =
the
> new calling convention. =A0Even when I use PHP to create page templates..=
.

Sounds like you're basically OK with that bit.

> Additional suggestions:
>
> Add an option so the CLI can start in code mode too.
>
> Add another Handler to the Apache SAPI, maybe application/x-httpd-php-cod=
e
> similar to x-httpd-php and x-httpd-php-source, so we can configure Apache=
 to
> start arbitrary file extensions with code mode on. =A0This defers setting=
 the
> action for various file extensions to the person configuring the web serv=
er.
>
> Other web server SAPIs will need similar treatment, but I'll leave them t=
o
> someone with personal experience.

I'm not opposed to these suggestions. I was trying to keep it
conservative and simple to implement and focus on the case where it
bugs me (creating libraries of class files), but I'd be happy to see a
way for .phpc to be the entry point / frontend controller / standalone
script as well. As you say it must be done with SAPI options (the CLI
included), not hardcoded file extension checking.

--=20
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com