Parsing rules

TQ White II tq at justkidding.com
Fri Nov 9 07:42:11 PST 2001


>quotes, and less-than signs inside a stretch of JavaScript need to be
>ignored. It's easier if you introduce the JavaScript during macro

FWIW

I use a great deal of macros for JS and PHP to generate code. However, I do
a lot of PHP and it's too hard to separate it and so I have made many
workarounds that did the job nicely, until now.

To deal with the general run of character problems, I use pseudo-codes for
the trouble characters and then process them out in finalFilter. For
example, in my universe, a curly brace is -(- or -)-. I have a whole suite
of these. (btw, I also use this technique to incorporate html in xml from a
database I use to organize an e-comerce application. XML hates angle
braces.)

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

Hitherto, I have only used these pseudocode where needed so that I can read
the code I write. That means always for curly braces and usually not for
angle braces (although a PHP start tag is always '\<' to allow macro
processing inside. It is only since F7 that I have had new problems.

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.

thanks,
tqii


--------------------------------------------------------------------------------
TQ White II

708/763-0100
tq at justkidding.com
http://www.justkidding.com

Check out my latest addition:
http://justkidding.com/politics
--------------------------------------------------------------------------------




More information about the Frontier-Users mailing list