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.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e384729507492509 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-11-03 12:07:49 PST Path: bga.com!news.sprintlink.net!hookup!news.mathworks.com!uhog.mit.edu!news.kei.com!world!blanket.mitre.org!linus.mitre.org!linus!mbunix!eachus From: eachus@spectre.mitre.org (Robert I. Eachus) Newsgroups: comp.lang.ada Subject: Re: Ada in Australia (was Ada ad in Embedded Systems Programming stinks) Date: 2 Nov 94 15:35:11 Organization: The Mitre Corp., Bedford, MA. Message-ID: References: <9410131051.AA29342@eurocontrol.de> <38neq3$9dg@f111.iassf.easams.com.au> <38us16$c0e@godzilla.zeta.org.au> <38v140$sdu@sunb.ocs.mq.edu.au> NNTP-Posting-Host: spectre.mitre.org In-reply-to: cperrott@krakatoa.mqcs.mq.oz.au's message of 30 Oct 1994 02:41:04 GMT Date: 1994-11-02T15:35:11+00:00 List-Id: In article <38us16$c0e@godzilla.zeta.org.au> andrewl@zeta.org.au (Andrew Lees) writes: > Where there have been problems, the root causes have been in the > management domain rather than the technical. This is so on both > of the projects that have had some difficulties. On the project > that has not had difficulties, the same applies: the reason for > its success has been consistently excellent management. In article <38v140$sdu@sunb.ocs.mq.edu.au> cperrott@krakatoa.mqcs.mq.oz.au (Chris Perrott) writes: > Well, yes and no. Ada 83 provides a way to get the address of a > procedure, but doen't provide a way to _call_ a procedure using > its address. Management decides that the project is to be done in > pure Ada, and forbids use of assembly language to call a procedure > using its address. Is it just me or did everyone spot the irony here? Ada 83 does provide mechanisms for calling procedures given addresses, and for that matter for embedding assembler. It's just that the stnadard (correctly) points out that these things are dependent on characteristics of the implementation . Good management reads this as a reason to encapsulate the dependencies in a limited part of the code, clueless management forbids the use. The most ridiculous example of this was a revision request for Ada 9X where the functionality requested was already provided by Unchecked_Conversion. The request was of course turned down. But the requestor responded that Unchecked_Conversion was not a solution--his company coding standards did not allow him to use it! The only good news in all this is that we have found that it is harder for poor (or worse) management of an Ada development project to get the project in a state where the only viable option is to cancel it. -- Robert I. Eachus with Standard_Disclaimer; use Standard_Disclaimer; function Message (Text: in Clever_Ideas) return Better_Ideas is...