Parsing rules

[TQ White II]

>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.

First, thanks for looking at this problem. I have often appreciated your
perspectives on matters Frontier, and am grateful for your interest.

As for the problem being elsewhere in the pipeline, it's not. I rely on
BBedit to determine how the problem is manifested. The examples I put in my
second note to Brent were extracted from BBedit after rendering from
Frontier--no other steps. I accept the possiblity that I have done
something else in Frontier (I do a lot of very complicated stuff) to cause
this but cannot, for the life of me, imagine what it could be.

(And I note, not out of ego but to explain, that I am a long time user of
Frontier and prepublication purchaser of your book, with years of
programming experience, a degree in ee/cs and the nickname 'der Bugmeister'
among some of my technical friends.)

It is worth noting that the use of angle braces in strings is different
than for your test. In particular, it's not in html. It's PHP. The angle
brace example is that I have a regex pattern that detects the stuff inside
an anchor tag, ie, the 'stuff' in '<A href=afdsafds>stuff</A>'. That
pattern opens with the left angle and closes with the right angle (more or
less), ie, ">[a-zA-Z0-9]{0,}data<". It doesn't work anymore unless I
'close' the final angle brace with a comment string, eg, //>.

I guess that my next step is to try to boil down an example into a minimal,
self contained example I can circulate. I'll look at that this weekend and,
if I succeed and you don't mind, send it your way.

Thanks again.
tqii


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

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

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