From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: G. B. Newsgroups: comp.lang.ada Subject: Re: Encaspulation: What to export Date: Wed, 29 Nov 2017 07:31:40 -0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 29 Nov 2017 07:31:40 -0000 (UTC) Injection-Info: reader02.eternal-september.org; posting-host="b990e4a5bffe4a60183dc40229179edb"; logging-data="23573"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+NeZ17FtOSIh/LCiaWoMQQGBIu6CB2OHA=" User-Agent: NewsTap/5.3 (iPhone/iPod Touch) Cancel-Lock: sha1:jzg5Xh0P6ieV1ytkP9Tg0ERvIhY= sha1:MxV5mYS3mT+4jxvp/Gf2g+rrwiQ= Xref: reader02.eternal-september.org comp.lang.ada:49236 Date: 2017-11-29T07:31:40+00:00 List-Id: Randy Brukardt wrote: >; SGML was > designed to not require parsing and all of these other formats kept the > basic design of SGML. SGML as opposed to misrepresentations of what is, by definition, and design, is configurable so as to support writers who like to omit, e.g. closing tags. This is just one example of when SGML may require substantial amounts of parsing in order to find the (set of) permissible sentence structures. Somewhat like an error correcting parser. I agree that a fail fast reader of a serialized tree is not a parser. Full SGML, it’s not-grammar-defining parts at least, is more like Markdown. The latter is notoriously hard to parse correctly, given the many ways in which writers can make reasonable mistakes which are therefore to be recognized and corrected , by Markdown parsers. Most are not mature enough to cope. And markdown typically doesn’t even have comments.