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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8893269a4640c798 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-07-24 08:42:43 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!proxad.net!peer1.news.newnet.co.uk!peer1.news.newnet.co.uk!borium.box.nl!fu-berlin.de!uni-berlin.de!tar-alcarin.cbb-automation.DE!not-for-mail From: Dmitry A. Kazakov Newsgroups: comp.lang.ada Subject: Re: terminate applications Date: Thu, 24 Jul 2003 17:46:59 +0200 Message-ID: References: <3F1C4DA6.3070405@attbi.com> <3F1D29E8.60107@noplace.com> <3F1D2FDC.1070402@noplace.com> <3F1DC75A.5050300@noplace.com> <87oezm9lar.fsf@inf.enst.fr> <3F1E7E1E.8090302@noplace.com> NNTP-Posting-Host: tar-alcarin.cbb-automation.de (212.79.194.111) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de 1059061361 18003998 212.79.194.111 (16 [77047]) X-Newsreader: Forte Agent 1.8/32.548 Xref: archiver1.google.com comp.lang.ada:40766 Date: 2003-07-24T17:46:59+02:00 List-Id: On Thu, 24 Jul 2003 10:54:51 -0400, "Warren W. Gay VE3WWG" wrote: >"Dmitry A. Kazakov" wrote in message news:ek2vhv4qcbtj4hspi2c0lojbtsh1baldql@4ax.com... >> On Thu, 24 Jul 2003 01:47:36 GMT, Hyman Rosen >> wrote: >> Probably the programmer has not done his homework. In a properly >> designed system there is no need in things like that. Even less Ada >> standard should encourage them. > >Perhaps, and perhaps not because it is due to an O/S bug where it >blocks on an O/S call when it should return an error. Things are not >always so cut and dry. The point is why your code should behave as Windows does? An Ada application can be and should be designed in a way allowing a graceful exit provided that underlying OS is OK. It means that the single reason why it might hang up is a call to some buggy OS API. If so, then you can well use another buggy API call to terminate it. Now, how this can support any need to incorporate that buggy API into the standard? Let operation F yelds an unpredictable result. Why one would like to call F? It would make WHAT? Isn't is Ariane 5 syndrome: (:-)) exception when Project_Mismanagement => --- Regards, Dmitry Kazakov www.dmitry-kazakov.de