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.1 required=5.0 tests=BAYES_20,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!mnetor!uunet!husc6!think!ames!ucbcad!ucbvax!VLSI.JPL.NASA.GOV!larry From: larry@VLSI.JPL.NASA.GOV Newsgroups: comp.lang.ada Subject: Rational "Gotcha's" + CASE stmt question Message-ID: <871214225653.00d@VLSI.JPL.NASA.GOV> Date: 15 Dec 87 06:56:53 GMT Sender: usenet@ucbvax.BERKELEY.EDU Organization: The ARPA Internet List-Id: ------------ We have just about decided to buy one of the smaller Rational systems and try it out on two real 3-5 person jobs to evaluate Ada as a mature technology. We'd want to get software--such as their CMVC (Config Mgt & Version Ctl) option--to cover the entire life cycle, not just hardware and compiler. What sort of things should we look out for in making the purchase that the sales people aren't likely to tell us (for malicious or innocent reasons)? This includes "gotcha's", third-party SW or HW, products or site- or training-preparations the sales people might not know about, etc. ------------ In several pieces of Ada SW recently I've seen CASE statements with dozens (in one case more than 200) alternatives. The longer ones often implement subprogram-dispatch tables. I know some compilers for other languages translate such statements into a hashed-jump routine. Is this often done by Ada compilers, or should programmers consider writing their own? ------------ Thanks in advance. Larry @ jpl-vlsi