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-Thread: a07f3367d7,c75fd3043cfdcb58 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.180.96.42 with SMTP id dp10mr1189452wib.2.1344263772485; Mon, 06 Aug 2012 07:36:12 -0700 (PDT) Path: q11ni72566922wiw.1!nntp.google.com!volia.net!news2.volia.net!feed-A.news.volia.net!border1.nntp.ams2.giganews.com!border2.nntp.ams2.giganews.com!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!nntp.giganews.com!news.panservice.it!news.ngi.it!diesel.cu.mi.it!newsfeed.x-privat.org!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: Jacob Sparre Andersen Newsgroups: comp.lang.ada Subject: Re: Formatted IO - Fortran style or similar. Date: Tue, 31 Jul 2012 13:56:14 +0200 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: <87lii06t5t.fsf@adaheads.sparre-andersen.dk> References: <50164ad8$0$1156$5b6aafb4@news.zen.co.uk> <501706ca$0$1151$5b6aafb4@news.zen.co.uk> NNTP-Posting-Host: monowall.adaheads.com Mime-Version: 1.0 X-Trace: munin.nbi.dk 1343735774 7065 77.234.168.91 (31 Jul 2012 11:56:14 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Tue, 31 Jul 2012 11:56:14 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Cancel-Lock: sha1:GU856JnsOPC/1a0ltI7WZmCai/s= Content-Type: text/plain; charset=us-ascii Date: 2012-07-31T13:56:14+02:00 List-Id: Dennis Lee Bieber wrote: > One of the goals for Ada was to put as much checking as possible into > the compiler... variable argument lists don't support that. Yes. How would you handle translatable user visible strings - such as "Parsing '${file_name}' failed on line ${line_number}." (where "${...}" identifies parameter substitutions) - in Ada? The standard library is definitely not (intended to be) the tool for that job. Two of the challenges are: + How can we (at compile-time) check that the named parameters in the translatable string match the parameters passed to the formatting routine? + How can we (at load-time) check that the parameters used in a translated string match those in the translatable string? Greetings, Jacob -- "There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies." -- C. A. R. Hoare