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: a07f3367d7,d1296b1e5055be50 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII Received: by 10.66.74.102 with SMTP id s6mr1687523pav.21.1344318771594; Mon, 06 Aug 2012 22:52:51 -0700 (PDT) Path: g9ni2590123pbo.0!nntp.google.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!ctu-peer!ctu-gate!news.nctu.edu.tw!usenet.stanford.edu!postnews.google.com!a7g2000pbm.googlegroups.com!not-for-mail From: wrp Newsgroups: comp.lang.ada Subject: Re: Ada folks need to talk to C++ folks more Date: Mon, 30 Jul 2012 17:10:34 -0700 (PDT) Organization: http://groups.google.com Message-ID: <2614e5fd-1f61-450a-b811-16fae3aa1e2a@a7g2000pbm.googlegroups.com> References: <6d4fedca-1b2f-476f-a05e-6c379389128b@wt8g2000pbb.googlegroups.com> NNTP-Posting-Host: 75.170.63.200 Mime-Version: 1.0 X-Trace: posting.google.com 1343693435 2723 127.0.0.1 (31 Jul 2012 00:10:35 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 31 Jul 2012 00:10:35 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: a7g2000pbm.googlegroups.com; posting-host=75.170.63.200; posting-account=_xNmGgoAAADzVbG1LIrTaXAR97KD43ZC User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.46 Safari/536.5,gzip(gfe) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-07-30T17:10:34-07:00 List-Id: On Jul 30, 1:34=A0pm, Simon Wright wrote: > wrp writes: > >http://www.250bpm.com/blog:4 > > You get the impression that the author's model of how to use exceptions > is somehow broken; I think he'd (mis)use exceptions the same way in Ada! That leads to the question of how many "language" issues are really "coder" issues.