ID:               49978
 Updated by:       [email protected]
 Reported By:      ronlentjes at yahoo dot com dot au
-Status:           Open
+Status:           Bogus
 Bug Type:         Scripting Engine problem
 Operating System: Linux Fedora 11
 PHP Version:      5.3.0
 New Comment:

You're couple of years too late. Still not a bug.


Previous Comments:
------------------------------------------------------------------------

[2009-10-23 23:03:35] ronlentjes at yahoo dot com dot au

Description:
------------
Please refer to old case (from another author):

Escaping curly braces produces backslash in output.

Bug #37263      Escaping curly braces produces backslash in output.

STATUS: Should not be bogus. It is a real issue not understood by PHP
staff. I do have a simple solution to this. Read on...

I noticed this bug come up in app.

I think you have misunderstood how bad this is and I consider this to
be a bug as well.

I understand you made a change so that \ infront of any character not
on the list of escapes will print \ with that offending character. This
is good.

All you have to do now is add { as an escape to the list so that \{
produces a single { that will solve all the problems. 

The original person who created this bug was trying to explain to you
that you gave no reasonable way ahead to fix old code and I think there
was miscommunication.

I too see this as a bug. What you missed in adding the VERY GOOD idea
of printing bad escapes, is the \{ has been a VALID ESCAPE in previous
versions. To fix this simply add { to your list of valid escapes and
produce a single { when encountered.

That will keep every one happy.

N.B. I now have to go through 1000's of lines of code and fix up every
occurance of this \{ which was realied apon as a very acceptable ESCAPE
sequence. (BUT NOW HAVE TO KEEP 2 VERSIONS!!)

Cheers,
Ron Lentjes
LC CLS.


Reproduce code:
---------------
When $ is involved:
{ -> nothing (0 chars)
\{ goes to \{ (2 chars)

This is illogical. How to go to just one character { in these
cases. No I don't accept \$ this is missing the point.


Expected result:
----------------
Please add { to list of acceptable ESCAPE sequences.
\{ -> always got to single { character and stop the following $
processing.

Effectively, this ESCAPE WAS in old version. But you didn't realize it
when you added code to produce BAD ESCAPES. You forgot that \{ was an
escape in old version.

So just add it and document it. 

That will solve all issues.



------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=49978&edit=1

Reply via email to