From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!hub1.nntpserver.com!feed.cgocable.net!news-hub.siol.net!newsfeed.Austria.EU.net!newsfeed.kpnqwest.at!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: The horror that is XML References: <3224334063725870@naggum.net> <3C8F7C2B.BC7D2A0F@erix.ericsson.se> Mail-Copies-To: never From: Erik Naggum Message-ID: <3225026478106156@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 22 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Mar 2002 16:41:06 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1016037666 193.71.199.50 (Wed, 13 Mar 2002 17:41:06 MET) NNTP-Posting-Date: Wed, 13 Mar 2002 17:41:06 MET Xref: archiver1.google.com comp.lang.lisp:28766 * Sverker Wiberg | So you might as well say | |
| (if (...condition...) | (...then...) | (...else...)) |
| | which would help cut down on the sugar intake. :D Good one! Yes, it is certainly possible to defer the whole problem to what SGML and XML call "notations", but the intention with notations was actually that they should have parsers that return structured objects. I doubt that anyone uses notations this way with the current crop of parsers, however. If someone knows, I would be happy to hear otherwise. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.