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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,6327f05d4989a68d X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 X-Received: by 10.66.82.164 with SMTP id j4mr5076008pay.15.1356837703533; Sat, 29 Dec 2012 19:21:43 -0800 (PST) Path: 6ni71719pbd.1!nntp.google.com!border1.nntp.dca.giganews.com!backlog1.nntp.ams.giganews.com!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!nntp.giganews.com!newsreader4.netcologne.de!news.netcologne.de!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: Press Release - Ada 2012 Language Standard Approved by ISO Date: Mon, 24 Dec 2012 07:44:00 +0100 Organization: Ada @ Home Message-ID: References: <7wrdmbre6jw9.qww9l0uzj6mg.dlg@40tude.net> <14oqoq06zhlu2.tcasif3hdyhw.dlg@40tude.net> <1drh1q1ln2dfh$.a9hwlg01fjfy.dlg@40tude.net> <50d6365d$0$6577$9b4e6d93@newsspool3.arcor-online.net> <1pbg79bz92j3t$.sz41zduivjfp.dlg@40tude.net> NNTP-Posting-Host: aWaWeUaBdaj2Zzc04J1v5A.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.11 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 X-Original-Bytes: 2716 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable Date: 2012-12-24T07:44:00+01:00 List-Id: Le Sun, 23 Dec 2012 09:08:53 +0100, Dmitry A. Kazakov = a =C3=A9crit: > Contracted exceptions is an urgent need. I agree this looks appealing, but Java already have the same and so some= = experiencing with it, and some Java people precisely have arguments = against it. May be worth to pull their arguments here. One I feel to = remember, is the exposition of implementation details which indirectly = comes with it (at least, one of their argument). Indeed, one may argue = they are the exceptions an implementation raise it self (either to match= a = contract or more freely) and they are the ones its dependencies may rais= e. = Some exceptions are under control, some are not. Think about an hardware= = failure during some processing, as an example=E2=80=A6 May be the contract, instead of specifying exhaustively what exceptions = a = sub=E2=80=91program may raises, could instead specify it may raise =E2=80= =9Cthis one=E2=80=9D, or = must not raise =E2=80=9Cthis other one=E2=80=9D, all other exceptions be= ing of unspecified = occurrence. Hope I'm clear enough (not sure to be) -- = =E2=80=9CSyntactic sugar causes cancer of the semi-colons.=E2=80=9D [1] =E2=80=9CStructured Programming supports the law of the excluded muddle.= =E2=80=9D [1] [1]: Epigrams on Programming =E2=80=94 Alan J. =E2=80=94 P. Yale Univers= ity