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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,ecc38b3271b36b88 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!news4.google.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!217.73.144.44.MISMATCH!ecngs!feeder.ecngs.de!border1.nntp.ams.giganews.com!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!nntp.giganews.com!news.mixmin.net!feeder.news-service.com!news.netcologne.de!ramfeed1.netcologne.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: What is the warning about builtin-function on gcc-4.6.0 ? Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <87aagiclte.fsf@mid.deneb.enyo.de> <475d10ca-5d4e-490c-9b88-e12cd3cd3faa@b13g2000prf.googlegroups.com> <87d3lejjyv.fsf@mid.deneb.enyo.de> <6c748f70-7e75-49b4-a467-d1d2d6b24323@w9g2000prg.googlegroups.com> <87tyeqi3h6.fsf@mid.deneb.enyo.de> <1n6308pk6569t.tyc9cc9l3fcn$.dlg@40tude.net> <5e721fd6-ee2c-4754-b09a-4a3b9c601bf3@l2g2000prg.googlegroups.com> Date: Sun, 27 Mar 2011 11:50:45 +0200 Message-ID: NNTP-Posting-Date: 27 Mar 2011 11:50:42 CEST NNTP-Posting-Host: 1fddd7e3.newsspool1.arcor-online.net X-Trace: DXC=J=A2F]bF2cVaAeROF2PWMQic==]BZ:af^4Fo<]lROoRQ<`=YMgDjhgRBegFcK<>=`^[6LHn;2LCV^[ On Sat, 26 Mar 2011 14:36:04 -0700 (PDT), ytomino wrote: > On Mar 27, 12:14�am, "Dmitry A. Kazakov" > wrote: >> When interfacing C, one IMO should always add a range or validity check >> when taking floating-point values from C, to prevent non-numbers leaking >> out. Unfortunately it is a lot of work, so no Ada bindings actually follows >> this rule. > > uh, there are functions (from C) that return infinity/NaN > intentionally, too. When a numeric function returns garbage it is useless. When non-numbers are supposed to serve error indication, they must be converted to an exception, e.g. Constraint_Error. Which is the whole point. In my view a C binding should check the result for mess and raise an exception if necessary. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de