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.1 required=5.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,6327f05d4989a68d X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII X-Received: by 10.181.13.205 with SMTP id fa13mr248943wid.3.1357956389606; Fri, 11 Jan 2013 18:06:29 -0800 (PST) MIME-Version: 1.0 X-FeedAbuse: http://nntpfeed.proxad.net/abuse.pl feeded by 78.192.65.63 Path: i11ni358866wiw.0!nntp.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!nntpfeed.proxad.net!news.muarf.org!news.ecp.fr!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Press Release - Ada 2012 Language Standard Approved by ISO Date: Fri, 11 Jan 2013 20:06:27 -0600 Organization: Jacob Sparre Andersen Research & Innovation 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><4c101d74-c8cb-45a6-82d4-91923bb950b0@googlegroups.com><87sj6tre9s.fsf@mid.deneb.enyo.de><895c9eb7-03f8-4b0c-96b4-3dbd7a315ccd@googlegroups.com> <87sj67r941.fsf@adaheads.sparre-andersen.dk> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1357956389 24682 69.95.181.76 (12 Jan 2013 02:06:29 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Sat, 12 Jan 2013 02:06:29 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Date: 2013-01-11T20:06:27-06:00 List-Id: "Jacob Sparre Andersen" wrote in message news:87sj67r941.fsf@adaheads.sparre-andersen.dk... > Yannick Duch�ne wrote: > >> I disagree a bit, and this case may suggest to use locks. > > Which file systems/operationg systems allow an application to take a > lock on a directory? Don't know of any! And *assuming* that only your application can create/modify a file is looking for trouble, as such an assumption could be violated by accident (some other program using a similar file naming scheme) or maliciousness. In the real world, there are lots of things that you can't know in advance -- you are always going to need a way to propagate run-time errors, which is what exceptions excel at (much better than error codes, IMHO). Randy.