Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59703
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAKOpQSzg5h539E341b5fyyUPj86Lf=E=r8B28PXrLcsj9O4RDw@mail.gmail.com>
References: <CAORXhGK47pRN8uUTENqSbddQoCP8VopomPhJW7N2pN6ZU8vNPQ@mail.gmail.com>
	<CAKOpQSz5tdkHK=MVsC8+8oL+Q-TGDAP=uBBC=i0p0pSJ4mn38Q@mail.gmail.com>
	<CAORXhGLppTWU9nRfhWLwRtHK_ct4SSLJxpwqAM0g6cnNirPSHA@mail.gmail.com>
	<CAKOpQSzg5h539E341b5fyyUPj86Lf=E=r8B28PXrLcsj9O4RDw@mail.gmail.com>
Date: Tue, 10 Apr 2012 23:35:17 -0400
Message-ID: <CAORXhGKwaCv-YoQ6TgEshtE2KQd0d_f8jrz3qYRDustA2eA58A@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] UPDATED RFC version 1.1: source files without opening
 <?php tag
From: tom@punkave.com (Tom Boutell)

On Tue, Apr 10, 2012 at 10:10 PM, Kris Craig <kris.craig@gmail.com> wrote:
> This shouldn't=A0be used to load libraries that dump raw HTML output! =A0=
That
> literally defeats the entire purpose. =A0You're also assuming that all PH=
P
> developers do 100% of their coding through pre-existing frameworks.

Consider a .phpp file that includes a .php template file when it sees
fit, in a render() method. How is this different from an echo()
statement? It's not. It's just a convenient form in some situations.
By punting these out to .php files we achieve better separation of
concerns while still respecting PHP's history as a template language
(and possible future if it improves in that area, which it may).

All I want is to stop typing <?php and dealing with whitespace
screwups above <?php. I want to do that in a way that's practical and
interoperable and which people might be able to vote for if they have
a nontrivial amount of legacy code in their life, like everybody I
work with (:

As many have pointed out, plain php template files work for some
projects. A viable RFC that people might actually vote for should
respect that. It neither picks my pocket nor breaks my leg if someone
wants to include .php template files from a .phpp file. I don't have
to do it.

When you consider that I would be completely unable to use an existing
.php library of nontrival code like Amazon's S3 SDK under your
proposal without a convoluted workaround it is pretty much a certainty
that I would have to vote no if the RFC read that way.

> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (Main Script)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|
> =A0 =A0 =A0 =A0 =A0[Included .php/HTML Script]
> =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |
> =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |
> {Included .phpp Script} =A0 =A0 =A0[Included .php/HTML Script from
> Framework/Library]

This is convoluted and forces me to write a .php frontend. Surely that
is not your goal.

--=20
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com