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=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c9d14a9b4208ef0b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-05-15 18:56:00 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-out.nuthinbutnews.com!propagator-sterling!news-in.nuthinbutnews.com!cyclone1.gnilink.net!wn3feed!wn2feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc01.POSTED!not-for-mail From: "Steve Doiel" Newsgroups: comp.lang.ada References: <3CE02EE1.8FEBD4DE@despammed.com> <3CE03784.DD40698E@despammed.com> <3CE14210.AC3FC998@despammed.com> <3CE2875B.F2A54C0D@despammed.com> Subject: Re: XML generator X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: NNTP-Posting-Host: 12.225.227.101 X-Complaints-To: abuse@attbi.com X-Trace: sccrnsc01 1021514159 12.225.227.101 (Thu, 16 May 2002 01:55:59 GMT) NNTP-Posting-Date: Thu, 16 May 2002 01:55:59 GMT Organization: AT&T Broadband Date: Thu, 16 May 2002 01:55:59 GMT Xref: archiver1.google.com comp.lang.ada:24142 Date: 2002-05-16T01:55:59+00:00 List-Id: "Wes Groleau" wrote in message news:3CE2875B.F2A54C0D@despammed.com... [snip] > DOM is merely an allegedly language-independent > specification of features that must be available > in the internal representation. Nothing about > writing out that I could see in the DOM spec. > Agreed. > And XML/Ada docs say that you'd have to write > callbacks to get anything out of a DOM tree. > Right. I just reviewed XML/Ada. While there are facilities to read a text file containing XML into a DOM tree (input_sources.file) there are currently no sources to write the DOM tree as a text file. If you contact ACT for support I'm sure they would be more than happy to put something together. > What I am trying to do is avoid future bugs > in a tool that currently writes XML as little > independent pieces. It has no concept of nesting > or of matching beginnings to ends, and so it's > very easy for a change to unintentionally make > the results invalid or malformed. > I don't know whether it would be an improvement over what you have, but writing recursive routine to dump the content of a DOM tree producing a valid XML file would (I think) be trivial. SteveD > -- > Wes Groleau > http://freepages.rootsweb.com/~wgroleau