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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,24d7acf9b853aac8 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,CP1252 Path: g2news1.google.com!postnews.google.com!g33g2000yqc.googlegroups.com!not-for-mail From: Natacha Kerensikova Newsgroups: comp.lang.ada Subject: Re: S-expression I/O in Ada Date: Mon, 9 Aug 2010 11:00:14 -0700 (PDT) Organization: http://groups.google.com Message-ID: <953773a2-6c4d-46e8-9947-4b50b17c71c7@g33g2000yqc.googlegroups.com> References: <547afa6b-731e-475f-a7f2-eaefefb25861@k8g2000prh.googlegroups.com> <1qk2k63kzh7yv$.3jgc403xcqdw$.dlg@40tude.net> <8ae8e899-9eef-4c8c-982e-bfdfc10072f1@h17g2000pri.googlegroups.com> <258zlxrv4fn6.1vszho1rtmf48$.dlg@40tude.net> <984db477-973c-4a66-9bf6-e5348c9b95f2@n19g2000prf.googlegroups.com> <5d0747cf-3226-4048-beb4-78b617fc19c9@v15g2000yqe.googlegroups.com> NNTP-Posting-Host: 95.152.65.220 Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1281376815 32325 127.0.0.1 (9 Aug 2010 18:00:15 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 9 Aug 2010 18:00:15 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: g33g2000yqc.googlegroups.com; posting-host=95.152.65.220; posting-account=aMKgaAoAAAAoW4eaAiNFNP4PjiOifrN6 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.3) Gecko/20100524 Firefox/3.6.3,gzip(gfe) Xref: g2news1.google.com comp.lang.ada:12996 Date: 2010-08-09T11:00:14-07:00 List-Id: On Aug 8, 5:24=A0pm, Robert A Duff wrote: > So Ada's overloading rules might be as complicated as the C++ > rules, but Ada _seems_ simpler, because you can safely ignore > all the details. =A0Unless you're writing an Ada compiler, of > course. I remember I wasn't that happy with C++ overloading, especially operator overloading. I wrote a 3D vector library only to find out operator overloading was more obscuring than improving readability, because too much was happening behind the scenes. So I came back to a math-assembly-looking sequence of function calls, uglier but easier to follow and maintain. > >...learning both Ada and AWS at the same time will > > probably be way too much. > > Well, I'm not sure. =A0To learn a programming language, you need to > write programs, and also read programs. =A0Jeff's point was that > reading AWS will help you learn Ada, and that's probably true. For some strange reason it didn't even occurred to be that the advice included reading AWS source and not only use it as a library. Still, AWS looks like an overkill for my web needs. > By the way, I don't see anything fundamentally wrong with > your s-expression plans, with s-expressions containing > raw arrays-of-octets Thanks for the support, that's what I'm about to do, except I'm still unsure about what array type to use: range octet, modular octet, Storage_Element, Stream_Element, something else=85 > -- especially since you say you > already have a lot of stuff using s-exprs. =A0You can layer on > top of that less-general but more-typed abstractions, probably > using generics. Actually I wasn't aware until very recently that the code I usually put on top of my S-expression parser is indeed called a parser too. So yeah, basically my S-expression library will be the common core of all my specialized configuration/template/etc file parsers. Natacha