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,d1df6bc3799debed X-Google-Attributes: gid103376,public From: eachus@spectre.mitre.org (Robert I. Eachus) Subject: Re: Language Design Mistakes (was "not intended...") Date: 1997/05/19 Message-ID: #1/1 X-Deja-AN: 243285352 References: <199705151433.OAA18453@sw-eng.falls-church.va.us> Organization: The Mitre Corp., Bedford, MA. Newsgroups: comp.lang.ada Date: 1997-05-19T00:00:00+00:00 List-Id: In article dewar@merv.cs.nyu.edu (Robert Dewar) writes: > The Ada 95 select .. then abort ... also introduces the same kind > of distributed overhead, but this time around, this overhead did > not seem to bother people (somewhat inexplicably if you ask me -- > this is my least favorite feature of Ada 95 -- and we have noticed > repeatedly that people use this construct without any idea of what > the consequences are, not only on efficiency, but more > particularly on program structure, and they are easily argued out > of using it!) T'FAILURE and "select ... then abort" both try to provide for the same need. However, no one could come up with a working example of code that used T'FAILURE. That is what washed it out of Ada 83. But the need was still there in 1993. Incidently, I am not convinced that there is any additional overhead attached to asynchronous abort that isn't there for the "normal" abort statement. It is just that the asynchronous abort stucture convinces people to actually use the beast in something other than a crowbar through the flywheel role. -- Robert I. Eachus with Standard_Disclaimer; use Standard_Disclaimer; function Message (Text: in Clever_Ideas) return Better_Ideas is...