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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00
	autolearn=no 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-21 20:13:31 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!diablo.theplanet.net!psiuk-p2!psiuk-p3!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail
From: "Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>
Newsgroups: comp.lang.ada
Subject: Re: XML generator
Date: Tue, 21 May 2002 13:43:07 -0400
Organization: Posted on a server owned by Pace Micro Technology plc
Message-ID: <ace0ve$epl$1@nh.pace.co.uk>
References: <3CE02EE1.8FEBD4DE@despammed.com>
 <abpcfc$9ve$06$1@news.t-online.com> <3CE03784.DD40698E@despammed.com>
 <3CE14210.AC3FC998@despammed.com> <zakE8.2533$gD6.4485@sccrnsc01>
 <3CE2875B.F2A54C0D@despammed.com> <usn4ticmy.fsf@wanadoo.fr>
 <3CE2DF3C.682F07C4@despammed.com> <ac0fq4$isb$1@nh.pace.co.uk>
 <slrnae8mcs.tev.aidan@crushed.velvet.net> <ac318a$9l6$1@nh.pace.co.uk>
 <slrnaebf9h.tev.aidan@crushed.velvet.net> <3CE92E3E.907E487F@despammed.com>
 <acbecu$mbf$1@nh.pace.co.uk> <usn4l4kdm.fsf@wanadoo.fr>
NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk
X-Trace: nh.pace.co.uk 1022002989 15157 136.170.200.133 (21 May 2002 17:43:10
 GMT)
X-Complaints-To: newsmaster@news.cam.pace.co.uk
NNTP-Posting-Date: 21 May 2002 17:43:10 GMT
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
Xref: archiver1.google.com comp.lang.ada:24498
Date: 2002-05-21T17:43:10+00:00
List-Id: <comp.lang.ada>

A "patch" in this case would pretty much amount to a rewrite. Its based on a
discriminated record. How could you realize an OO implementation based on a
"Node" class with descendents for all the different XML elements without
pretty much annihilating everything that is already there? Check out the
description of DOM level 1 here:
http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/level-one-core.html#ID-BB
ACDC08 and you'll notice that the XMLAda implementation - while it may
satisfy the requirements - doesn't exactly follow in the spirit of
everything inheriting from a Node class. I'm not criticizing - just
observing that a more OO design could have been done that would line up
better with the spec. Changing something this fundamental would likely
butcher it.

Even if you could somehow re-map the whole thing into tagged records with
inherited operations, you'd be dramatically changing the interface which
would kill anything currently using it. You could certainly salvage large
chunks of code but I'd think it would be better to develop one from bottom
dead center than to try to hammer XMLAda into a whole different mold.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com


"Pascal Obry" <p.obry@wanadoo.fr> wrote in message
news:usn4l4kdm.fsf@wanadoo.fr...
>
> Not a problem, just propose a patch to have XMLAda more OO... No kidding,
> XMLAda is ours, it is up to us to make it better...
>