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,7624df5e57d09688 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-06-02 14:29:15 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!nycmny1-snh1.gtei.net!news.gtei.net!news-out.visi.com!hermes.visi.com!cox.net!news-east.rr.com!cyclone.kc.rr.com!news.kc.rr.com!cyclone3.kc.rr.com!news3.kc.rr.com!twister.socal.rr.com.POSTED!not-for-mail Message-ID: <3CFA8E42.B7844253@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: config files proposal References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 02 Jun 2002 21:29:14 GMT NNTP-Posting-Host: 66.75.151.160 X-Complaints-To: abuse@rr.com X-Trace: twister.socal.rr.com 1023053354 66.75.151.160 (Sun, 02 Jun 2002 14:29:14 PDT) NNTP-Posting-Date: Sun, 02 Jun 2002 14:29:14 PDT Organization: RoadRunner - West Xref: archiver1.google.com comp.lang.ada:25220 Date: 2002-06-02T21:29:14+00:00 List-Id: Stephen Leake wrote: > http://users.erols.com/leakstan/Stephe/Ada/config_files.html I would suggest using Wide_String for keys. (API#8) You need to specify where a file is written in the path. (API#6) apparently only talks about reading files. FF #1 has to deal with the differences between systems anyway. Character sets, newlines, etc. Or at least mention what you mean. That is, file format #1 kind of conflicts with file format #2, if Text_IO writing on one system isn't readable on another. FF #3 I would disagree with. It limits having large items in the config file format. Making key/value pairs terminated by a newline is specifying the implementation. It doesn't make any sense to do such a thing in XML, for example. Perhaps starting continuation lines with a space as is done in RFC 822 headers would make more sense. In addition, API#15 conflicts with this requirement. FF#4 should be written as "leading and trailing whitespace on keys and values is semantically meaningless". Question: Are keys case-sensitive? Question: What about where most of the configuration is stored in a system-wide file, with individual users capable of overriding particular entries? Kind of like /etc/bashrc and ~/.bashrc on Linux? Question: Does the file automatically flush changes as it goes out of scope? (API#4) Question: Is the file closed (w.r.t. the OS) between the end of the read and the start of the write? Question: Would it make sense to allow compound values to be written by converting a stream of them to base64 or something? -- 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.