Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91846
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.50 as permitted sender)
MIME-Version: 1.0
References: <CACNm7o9-6z0rxAAxnWyUFhYU+YD-QnecWrJF-PQ=z+a9qNQ=EA@mail.gmail.com>
 <CAGa2bXbjNQXwVsFmGgFVUPCFV-t2Tye+xA3MDNpA_ydjvCQ3jA@mail.gmail.com>
 <CACNm7o9NNVFrgqeufBoDgyhE-eGQix6bZwq=XGVwsROSXVb5Ag@mail.gmail.com>
 <op.yep7fksgzsg2np@hnb2> <CADyq6s+=DtuqVghNpXVT9t4rgLFp4tM3KGqv4ki+ZFwKiVzeEg@mail.gmail.com>
 <op.yep74rkmzsg2np@hnb2> <CAHE1Edtn_cQuUUMEt5zgj6Y-UaKSB0u8A5WNXm=+m_F2-N9-3A@mail.gmail.com>
 <op.yep98qw9zsg2np@hnb2>
In-Reply-To: <op.yep98qw9zsg2np@hnb2>
Date: Tue, 22 Mar 2016 14:43:37 +0000
Message-ID: <CAJaRsPtCNNLAy48LmGpy7jxAwMiWcwBpfJxkX7KosycLvCPV-A@mail.gmail.com>
To: =?UTF-8?Q?Jan_Tvrd=C3=ADk?= <j.tvr@centrum.cz>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a11c02514a22376052ea43d14
Subject: Re: [PHP-DEV] RFC about automatic template escaping
From: colinodell@gmail.com ("Colin O'Dell")

--001a11c02514a22376052ea43d14
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Daniel,

This is a really interesting idea!  However, I'm unsure whether it's wise
to bring this feature in without having the community test and validate it
first.  Would it be possible to release this as an extension first so we
can gauge its stability and desirability in "the real world"?

As far as the implementation goes, one thing I don't like is the complexity
involved to output unescaped HTML.  I'd strongly prefer to do something
like <?=3Draw($someVariable) ?> than having to instantiate a special class
every time I need to output some raw HTML.

Also, I know some templating systems (like Twig) allow you to specify
different escaping strategies:
http://twig.sensiolabs.org/doc/filters/escape.html  Would this proposed
feature have any similar functionality?

Best regards,

Colin

On Tue, Mar 22, 2016 at 9:26 AM Jan Tvrd=C3=ADk <j.tvr@centrum.cz> wrote:

> On Tue, 22 Mar 2016 14:01:09 +0100, Craig Duncan <php@duncanc.co.uk>
> wrote:
>
> >>
> >>
> >> Why do you assume that Latte parser is limited by regexp ability to
> >> parse
> >> HTML?
> >
> >
> > Because it is:
> >
> https://github.com/nette/latte/blob/19b759b550caaad75ca0dee5f0d85f9ffb59c=
845/src/Latte/Parser.php#L124
>
> No. That argument would only be valid, if the parser consisted only of a
> single regexp. When you combine PHP code with PCRE you loose nothing from
> PHP's turing completeness and it's ability to parse HTML.
>
> That being said I'm not claiming that Latte parser is 100 % correct HTML
> parser (neither is most existing HTML parsers in the world). I'm saying
> that it could be (to the extend of what's possible to statically analyze,
> i.e. if editor could highlight the code properly).
>
> Regards,
> Jan Tvrdik
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a11c02514a22376052ea43d14--