Hi!
Right, I think that is actually the conclusion we came to at one point.
I don't remember the discussion that caused the RFC to be declined. I
would be in favour of reversing that decision wherever it came from.
Amen to that!
And that just isn't going to happen. The only valid
On Fri, Jun 5, 2009 at 07:47, Rasmus Lerdorfras...@lerdorf.com wrote:
Nobody is going to pass a PHP script through an XML parser, and PHP
itself will never be well-formed, so that is a lost cause. We'd have to
start tossing CDATA blocks and write code like:
if( 2 lt; 3 ) echo 2 is less than
Hannes Magnusson wrote:
On Fri, Jun 5, 2009 at 07:47, Rasmus Lerdorfras...@lerdorf.com wrote:
Nobody is going to pass a PHP script through an XML parser, and PHP
itself will never be well-formed, so that is a lost cause. We'd have to
start tossing CDATA blocks and write code like:
if( 2
Hi,
Plain ? has an additional problem of affecting the ability to include XML
files from PHP source code.
readfile('file.xml');
From what I know, in the future versions of PHP short tags are going to be
disabled by default. Considering the conflicts with XML syntax, that's
understandable.
On Jun 5, 2009, at 12:53 AM, Rasmus Lerdorf wrote:
Hannes Magnusson wrote:
On Fri, Jun 5, 2009 at 07:47, Rasmus Lerdorfras...@lerdorf.com
wrote:
Nobody is going to pass a PHP script through an XML parser, and PHP
itself will never be well-formed, so that is a lost cause. We'd
have to
Hi!
So it feels like decoupling ?= from short_open_tag is on the table.
Rasmus or Stas, could you please propose exactly how this might happen?
My proposal would be very simple:
1. short_open_tag setting removed in 6, ? is no longer PHP code tag
under any circumstances.
2. ?= is always
On 6/5/09 2:17 PM, Stanislav Malyshev wrote:
Hi!
So it feels like decoupling ?= from short_open_tag is on the table.
Rasmus or Stas, could you please propose exactly how this might happen?
My proposal would be very simple:
1. short_open_tag setting removed in 6, ? is no longer PHP code tag
Hi!
No, #1 in your list is why people got sick of it. You want to bind the
decoupling of ?= as a short tag to the removal of short tags. They are
two different issues.
I do not insist on 1. I'd be ok with not touching short tags but just
moving ?= to non-short. I just think once ?= is
Philip Olson wrote:
On May 30, 2009, at 12:49 PM, Roman I wrote:
Philip Olson wrote:
On May 18, 2009, at 5:33 PM, Roman I wrote:
This neither answers nor invalidates the original question, though.
Unfortunately I do not remember everything about this but do know that:
- Decoupling
Roman I wrote:
Philip Olson wrote:
On May 30, 2009, at 12:49 PM, Roman I wrote:
Philip Olson wrote:
On May 18, 2009, at 5:33 PM, Roman I wrote:
This neither answers nor invalidates the original question, though.
Unfortunately I do not remember everything about this but do know that:
-
On May 30, 2009, at 12:49 PM, Roman I wrote:
Philip Olson wrote:
On May 18, 2009, at 5:33 PM, Roman I wrote:
From what I know, in the future versions of PHP short tags are going
to be
disabled by default.
snip
Common misunderstanding but the short_open_tag directive will never
be
In summary: It's a topic people don't want to talk about. :)
The ?= issue is really quite significant however, it seems quite a
common topic of confusion at freenode's ##php. Lots of ZF examples and
other mainstream code uses ?= and it seems a very good idea to use
it... however it's very
Philip Olson wrote:
On May 18, 2009, at 5:33 PM, Roman I wrote:
From what I know, in the future versions of PHP short tags are going
to be
disabled by default.
snip
Common misunderstanding but the short_open_tag directive will never be
disabled by default. There are distributed
From what I know, in the future versions of PHP short tags are going to be
disabled by default. Considering the conflicts with XML syntax, that's
understandable. However, is there a technical reason to consider ?= a
short tag? From what I know, it doesn't conflict with XML notation, and it
is
14 matches
Mail list logo
