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,a26758eec3c2e1ad X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-06-19 09:43:17 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed1.cidera.com!Cidera!cyclone.columbus.rr.com!cyclone3.kc.rr.com!news3.kc.rr.com!twister.socal.rr.com.POSTED!not-for-mail Message-ID: <3D10B4C1.CFB7805B@san.rr.com> From: Darren New X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Use of XML for config files References: <3D0769F7.68F5BD9C@san.rr.com> <4519e058.0206130553.3ee195f1@posting.google.com> <3D08CAF0.846AA176@san.rr.com> <3D08E539.343A42BF@san.rr.com> <3D0A2686.785D1BAC@san.rr.com> <3D0F53CC.E3CBB193@san.rr.com> <3D0FAA84.ED827CF5@san.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 19 Jun 2002 16:43:17 GMT NNTP-Posting-Host: 66.75.151.160 X-Complaints-To: abuse@rr.com X-Trace: twister.socal.rr.com 1024504997 66.75.151.160 (Wed, 19 Jun 2002 09:43:17 PDT) NNTP-Posting-Date: Wed, 19 Jun 2002 09:43:17 PDT Organization: RoadRunner - West Xref: archiver1.google.com comp.lang.ada:26397 Date: 2002-06-19T16:43:17+00:00 List-Id: Georg Bauhaus wrote: > : Having a very explicit file format finalized before anyone > : even decides what the API looks like is kind of silly. > > Well, OTOH, file formats do have consequences for what you can reasonably > want to be present in an API don't they? Yes. But what are we more concerned with? The file format, or what you can do with the file format? If the file format is already fixed, then trying to come up with the best API to manipulate it is a worthwhile exercise. When the question is "what are we doing here", assuming the file format is fixed is probably a bad idea. I suspect it's so obvious to you how you'd use something like this that some of us appear very dense or blind or something. It's simply that you already have a good idea of the API in your head you just haven't revealed. Clearly everything in Stephen's discussion could be implemented either way. You haven't said just what it is you couldn't implement with a format less complex than XML. That's what I'm looking for. -- Darren New San Diego, CA, USA (PST). Cryptokeys on demand. ** http://home.san.rr.com/dnew/DNResume.html ** ** http://images.fbrtech.com/dnew/ ** My brain needs a "back" button so I can remember where I left my coffee mug.