Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59833
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAGa2bXaaSs_Y1cZPWezinZSeqXEeAB3Qq-VMzMkHHHJXu_DOqA@mail.gmail.com>
References: <CAKOpQSwYe+tZ3JfLFWaOHCnBpUyy9yoA61=qLzbnnOKTL0mQdQ@mail.gmail.com>
 <CAGa2bXaaSs_Y1cZPWezinZSeqXEeAB3Qq-VMzMkHHHJXu_DOqA@mail.gmail.com>
Date: Fri, 13 Apr 2012 10:10:32 +0900
Message-ID: <CAGa2bXaTudm0Pfpc-udL_fchoR-644PcPwFWAMk0niLn3WtJpw@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] New .phpp File Type for Pure-Code PHP Scripts
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

2012/4/13 Yasuo Ohgaki <yohgaki@ohgaki.net>:
> Hi,
>
> If we aren't going to consider saving current code risk, then
> we could use both new include and file name convention.
>
> Introduce application/x-httpd-php-script, then we could
>
> AddHandler php5-script .php
> AddType text/html .php
> AddType application/x-httpd-php-source .phps
> AddType application/x-httpd-php-script =A0 .ph // .phpp .phpc .phpscript
> whatever extension here
>
> We may need ENV vars for other SAPIs.
>
> script/script_once for PHP only script includes.
>
> How about this?

Forgot to mention CLI.
CLI switch for script only should be included.
Putting all 3 RFC together may work as long as
basic semantics is the same.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net