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,d6f7b92fd11ab291 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-07-15 22:03:01 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news.airnews.net!cabal12.airnews.net!usenet From: "John R. Strohm" Newsgroups: comp.lang.ada Subject: Re: Crosspost: Help wanted from comp.compilers Date: Tue, 15 Jul 2003 23:45:46 -0500 Organization: Airnews.net! at Internet America Message-ID: References: <1058275843.720814@master.nyc.kbcfp.com> <3F14B061.1040802@spam.com> Abuse-Reports-To: abuse at airmail.net to report improper postings NNTP-Proxy-Relay: library2.airnews.net NNTP-Posting-Time: Wed, 16 Jul 2003 00:01:56 -0500 (CDT) NNTP-Posting-Host: !`A_<1k-WiObNVM (Encoded at Airnews!) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Xref: archiver1.google.com comp.lang.ada:40324 Date: 2003-07-15T23:45:46-05:00 List-Id: "Jeffrey Carter" wrote in message news:3F14B061.1040802@spam.com... > John R. Strohm wrote: > > > > Now, it was EASY to build systems that had horrendous recompilation > > problems. Usually, in order to build such a system, you had to screw up > > some fairly basic software engineering things. For example, if you build a > > system-wide "types" package, then every time you touch that package, you get > > to recompile the world. If you build a system-wide "magic numbers" package, > > same problem. Observe that the exact same problems arise in C/C++. The > > answer is, of course, DON'T DO THAT. > > These are fairly benign problems. I know of at least one current DoD > project that has a system-wide "variables" package. This software is > flying in a state-of-the-art military aircraft. Not only do most > upgrades involve modifying this package, and hence recompiling the > entire system, but the system is 100% coupled with 0% cohesion. > Understanding the system from scratch is at least as expensive as > redesigning and rewriting the entire system; that's the choice they will > face if the couple of developers, who have been there from the beginning > and have the entire system in their heads, ever quit or are killed going > out to lunch together. I am not at all surprised to hear this. Sometimes you run into that kind of overcoupling and undercohesion because of timeline/fairness concerns. The system designer has to guarantee that every task DOES get his assigned timeslice, every time, or things can go to hell in a handcart in a hell of a hurry. You want a horrible example? Calculate a dive toss delivery, and see just how small your release time window really is. And EVERYTHING has to run, in the right order, to calculate the delivery and decide when to tell the latches to let go of the bomb. And then the actual release message has to get out to the latches on the rack... I am curious, though. Can you say what project it is?