Parsing rules

[Matt Neuburg]

At 9:57 PM -0600 11/8/01, thus spake TQ White II:

>The reason that I am having trouble these days is thatsomething has
>changed. It used to be that I could have angle braces inside quoted strings
>with no problem. Not any more.

This phrase:

   "test of this<>"

Renders as

   "test of this<>"

The phrase:

   "<test>"

Renders as

   "<test>"

but of course in the browser it shows as "" because <test> is 
interpreted as an HTML tag.

So I would say that angle braces inside quoted strings work just fine 
in Frontier. Perhaps what's changed is your browser, or your 
browser's interpretation of HTML. This was an illegal string from the 
start, on any interpretation of HTML; I should have been using &lt; 
and &gt; obviously. It was never Frontier's responsibility to make 
that change; it's my job to do it in the HTML.

>I used to be able to use \n\r for newline
>carriage-return in PHP quoted strings with no problem. Not any more.

The phrase

    This is a "\n\r"

renders as

    This is a "\n\r"

>I'm not against using techniques to work around Frontier's string
>processing. It's just that I have thousands of lines of code that don't
>work right anymore and it's a really bad thing to have that much stuff
>broken.

I'm suggesting, though, that perhaps it's another place in the 
pipeline where things have changed, since I can't reproduce the 
problems you describe. m.

-- 

matt neuburg, phd = matt at tidbits.com, http://www.tidbits.com/matt
pantes gar anthropoi tou eidenai oregontai phusei