home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!charnel!rat!usc!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!uicvm.uic.edu!u35395
- From: U35395@uicvm.uic.edu (C. M. Sperberg-McQueen)
- Newsgroups: comp.text.sgml
- Subject: Re: Precedence of SGML Operators?
- Message-ID: <93005.142005U35395@uicvm.uic.edu>
- Date: 5 Jan 93 20:20:04 GMT
- References: <1802@igd.fhg.de> <19921228.013@erik.naggum.no>
- Organization: University of Illinois at Chicago
- Lines: 24
-
- Erik Naggum writes:
- > ... which in a different language could have
- > been explained by some arcane precedence rules at work; however, SGML
- > has no notion of operators or of operator precedence rules as these
- > terms are used in programming languages.
-
- I think EN strains things a bit here, with potentially misleading
- results. SGML indeed has 'no notion of [...] operator precedence' but
- this does not mean Holger Rath's query was ill-formed! The fact that
- SGML expresses its operator precedence rules in its formal grammar
- rather than in separate rules (as for example yacc does) does not mean
- SGML has no operator precedence, only that its operator precedence
- rules are implicit.
-
- The analyses posted already seem to me to hit the case: looks like
- a bug in Mark-It.
-
- By the bye: EN's remarks might lead one to believe that other SGML
- parsers don't have bugs; that would be a wrong conclusion. Certainly
- most of the ones I've used have a problem here or there.
-
- -C. M. Sperberg-McQueen
- ACH / ACL / ALLC Text Encoding Initiative
- University of Illinois at Chicago
-