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 13:33:55 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.freenet.de!eusc.inter.net!cs.tu-berlin.de!uni-duisburg.de!not-for-mail From: Georg Bauhaus Newsgroups: comp.lang.ada Subject: Re: Use of XML for config files Date: Wed, 19 Jun 2002 20:33:54 +0000 (UTC) Organization: GMUGHDU Message-ID: References: <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> <3D10B4C1.CFB7805B@san.rr.com> NNTP-Posting-Host: l1-hrz.uni-duisburg.de X-Trace: a1-hrz.uni-duisburg.de 1024518834 28538 134.91.4.34 (19 Jun 2002 20:33:54 GMT) X-Complaints-To: usenet@news.uni-duisburg.de NNTP-Posting-Date: Wed, 19 Jun 2002 20:33:54 +0000 (UTC) User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (HP-UX/B.11.00 (9000/800)) Xref: archiver1.google.com comp.lang.ada:26437 Date: 2002-06-19T20:33:54+00:00 List-Id: Darren New wrote: : : 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. Please, not at all, in fact (as always, no?) you have reminded me of some things to consider. : 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. Point is that personally I am fine with a complex format or a less complex format. What's bothering me is not so much what can be implemented in either format _for Config_Files.ads_, or how the application programmer would use the subprograms, but it is that the configuration process consists of more than an API, a file format, and text editors. How can I improve the "human aspect" of configuration processes using what is available with some file format? (my reply to Stephen has a few words on this, I hope) The current API has dotted notation. That's a very clear, powerful and manageable thing from an application's point of view, Stephen has working software for property files and XML files. I have nothing to complain here. If you can say that dotted notation in the config file _itself_ is likely not a problem at all for your usual configuration personnel, then don't weigh my words too much, maybe my needs are too far reaching for the average Ada application (or way off :). -- Georg