Peter Eisentraut wrote: > On l?r, 2011-09-03 at 16:47 -0400, Bruce Momjian wrote: > > Peter Eisentraut wrote: > > > On tor, 2011-09-01 at 17:31 -0400, Bruce Momjian wrote: > > > > Peter Eisentraut wrote: > > > > > On tor, 2011-09-01 at 14:17 -0400, Bruce Momjian wrote: > > > > > > > That still leaves open why we bother about escaping <. > > > > > > > > > > > > The problem is that I often add SGML that has: > > > > > > > > > > > > if (1 < 0) ... > > > > > > > > > > > > I need something to warn me about those, especially in the release > > > > > > notes. > > > > > > > > > > Why do you need to be warned about that? > > > > > > > > If I have: > > > > > > > > if (1 < fred) > > > > > > > > it will think "fred" is a SGML tag, no? > > > > > > No, a < followed by a space is not a tag, it's character data. If it > > > thought it were a tag, it would complain. > > > > Sometimes it is '<' (in single quotes), which I thought would be a > > problem. > > The bottom line is, the SGML parser can figure that out itself, and if > it has a problem, it will complain. We don't need to second guess it > with regular expressions that are handcrafted out of thin air. > > I was hoping you would remember whether you initially put this in > because of some tool problem. But if we are not finding any supporting > evidence, I would suggest that we just scrap this thing entirely.
I put it in to warn about release.sgml markup problems, so I properly escaped all non-tag '>' and '<' characters. I have removed the tool. We can always re-add it if we find it is needed. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
