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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,fac1372a6e25492a X-Google-Attributes: gid103376,public From: Tucker Taft Subject: Re: Ada Protected Object Turorial #2: Overview of Tasks Date: 1999/12/20 Message-ID: <385E9343.1D23B0C5@averstar.com>#1/1 X-Deja-AN: 563123996 Content-Transfer-Encoding: 7bit Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.burl.averstar.com References: <83hu2h$bba$1@bgtnsc01.worldnet.att.net> <83j1g0$ck4$1@nnrp1.deja.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: AverStar (formerly Intermetrics) Burlington, MA USA Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-12-20T00:00:00+00:00 List-Id: Robert Dewar wrote: > ... > All in all, a good rule in Ada 95 is not to use ATC. My view is that ATC is dangerous, but important in some situations where polling is impractical. It is somewhat safer than setjmp/siglongjmp, which is a standard, and relatively frequently (mis?)used, feature of ANSI C and POSIX. Note that most "production quality" database systems operate under the presumption that the power cord can be unplugged at any moment. Abort is somewhat less catastrophic than that... > ... > > I just trimmed this to CLA, since it is rather too Ada specific > for comp.threads. And politically incorrect ;-) > > Robert Dewar -- -Tucker Taft stt@averstar.com http://www.averstar.com/~stt/ Technical Director, Distributed IT Solutions (www.averstar.com/tools) AverStar (formerly Intermetrics, Inc.) Burlington, MA USA