Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36300
Return-Path: <auroraeosrose@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 90603 invoked from network); 21 Mar 2008 21:53:26 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 21 Mar 2008 21:53:26 -0000
X-Host-Fingerprint: 24.247.219.180 24-247-219-180.dhcp.cdwr.mi.charter.com  
Received: from [24.247.219.180] ([24.247.219.180:15589] helo=localhost.localdomain)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 68/F2-26785-55E24E74 for <internals@lists.php.net>; Fri, 21 Mar 2008 16:53:25 -0500
Message-ID: <68.F2.26785.55E24E74@pb1.pair.com>
To: internals@lists.php.net
Date: Fri, 21 Mar 2008 17:53:19 -0500
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
References: <47E3F714.60302@zend.com>  <883216194.20080321193140@marcus-boerger.de>  <47E40848.1060103@zend.com> <47E40C3F.8040601@sci.fi>  <47E40E6E.5030103@zend.com> <47E410C6.80605@sci.fi>  <47E4146A.8010409@zend.com> <fe05d1540803211313j22578632rfabe22f53592eb6d@mail.gmail.com> <47E41765.4080007@zend.com> <111239762.20080321212310@marcus-boerger.de> <47E41C9F.4040105@zend.com> <935033306.20080321223836@marcus-boerger.de>
In-Reply-To: <935033306.20080321223836@marcus-boerger.de>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Posted-By: 24.247.219.180
Subject: Re: [PHP-DEV] short_open_tag
From: auroraeosrose@gmail.com (Elizabeth M Smith)

Wow, noisy...

I've been in the situation where I use php for templating and the short
syntax is much nicer on the eyes.  The ability to "flick the switch" for
short tags would be nice.

However, like Steph, I've also been bitten by having a simple xml
declaration in a file with short tags on that completely breaks things.
Parse errors are NOT a good thing.  This is why I'd personally prefer
short tags just go poof - having to check all your code so any
appearance of <? is echo'd gets really annoying.

I'd argue that a <?php= shortcut or something similar would help "split
the difference" between the ugliness of the long version and the need to
not break php every time an xml declaration pops up in a file.  Even
gettext has a nice _() function shortcut which is less typing than echo
$blah; in every php tag set, and then you wouldn't be fighting with the
potential breakage.  The argument that if some new syntax only goes into
5.3, people can't use it doesn't really hold water here because you
wouldn't be able to rely on flipping the short_tags switch before 5.3
either.

I can see both sides of the story, and really don't have a preference -
I'm curious as to the opinions of someone OTHER than Marcus, Stas,
Pierre and Jani ;)

Thanks,
Elizabeth M Smith