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,f3bebae566a54cab X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Fri, 24 Jun 2011 12:41:55 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110613 Thunderbird/3.1.11 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Some exciting new trends in concurrency and software design References: <8a5765ba-622a-42cd-9886-28ed7cfed31e@s17g2000yqs.googlegroups.com> <4dff5be5$0$6565$9b4e6d93@newsspool3.arcor-online.net> <9b65f3c7-caee-440f-99ed-0b257221ce58@m24g2000yqc.googlegroups.com> <1v2auyktde5q4.1wqpdg3fval5k.dlg@40tude.net> <4e03bb73$0$6584$9b4e6d93@newsspool3.arcor-online.net> <1fb2bb30-a267-4e19-b4c6-08c35d74484a@u7g2000yqc.googlegroups.com> In-Reply-To: <1fb2bb30-a267-4e19-b4c6-08c35d74484a@u7g2000yqc.googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4e0469f4$0$6582$9b4e6d93@newsspool3.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 24 Jun 2011 12:41:56 CEST NNTP-Posting-Host: f9c9521f.newsspool3.arcor-online.net X-Trace: DXC=[RU\iiiHj38Tia]Ho99G50McF=Q^Z^V384Fo<]lROoR18kFejV8aY[:oKF\Qm?XkKjN==jYk0 X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:20995 Date: 2011-06-24T12:41:56+02:00 List-Id: On 6/24/11 3:26 AM, Phil Clayton wrote: > Arbitrary magnitude integers are supported in at least SML, OCaml and > Haskell. They are supported, yes, my point was, however, that special effort is required: if a program uses "plain" ATS/O'Caml integers, it will easily run into erroneous execution. I am assuming that this was neither the programmer's intent, nor was it the intent of language designers who add a proof system to their language. It seems, then, that the designers have ignored this aspect of C int, which they have used. It doesn't seem right to let C int be the default for such a language.