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=-2.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Thread: 103376,deac256a05c84a59 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!proxad.net!usenet-fr.net!enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: "amado.alves" Newsgroups: comp.lang.ada Subject: RE: DOM and SAX parsing in Ada Date: Tue, 25 Jan 2005 00:22:34 -0000 Organization: Cuivre, Argent, Or Message-ID: NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: melchior.cuivre.fr.eu.org 1106612579 39331 212.85.156.195 (25 Jan 2005 00:22:59 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Tue, 25 Jan 2005 00:22:59 +0000 (UTC) To: "Georg Bauhaus" , Return-Path: X-MIMEOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: DOM and SAX parsing in Ada Thread-Index: AcUCUiwhkYFFXhvXSYCX0OTGhOGpoQAH571d X-OriginalArrivalTime: 25 Jan 2005 00:22:34.0990 (UTC) FILETIME=[F7AF90E0:01C50273] X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Gateway to the comp.lang.ada Usenet newsgroup" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: g2news1.google.com comp.lang.ada:7968 Date: 2005-01-25T00:22:34+00:00 >> ... http://softdevelcoop.org/software/xml_automaton ... =09 > Let me be picky, it is a tokenizer of straightforward simplicity... Yes, strictly it's a tokenizer. I stand corrected. I called it parser = because the damn thing is more than 50% of the XML parsers I write using = it. Because to me a general purpose XML parser makes little sense. It = just translates from one tree representation to another. And there is a = zillion possible target representations. DOM, Yaml, many database = languages, Booch containers, Ada 2005 containers, iterators, = combinations thereof... I leave the choice to application time. And then = what I need is a tokenizer. A straighforward, simple, effective, usable, = robust, superfast one :-)