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,3f02741d8aff850b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-10-05 09:46:38 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!howland.reston.ans.net!swrinde!elroy.jpl.nasa.gov!lll-winken.llnl.gov!noc.near.net!inmet!dsd!stt From: stt@dsd.camb.inmet.com (Tucker Taft) Subject: Re: ClearCase and Ada -- Config. Management Message-ID: Sender: news@inmet.camb.inmet.com Organization: Intermetrics, Inc. References: <36hjek$18k@hacgate2.hac.com> Date: Wed, 5 Oct 1994 13:07:04 GMT Date: 1994-10-05T13:07:04+00:00 List-Id: ClearCase should work relatively well with Ada compilers that have a source-based library, such as GNAT. However, if the compiler maintains an intermediate database, everything will probably end up being dependent on central parts of the database that are continually changing (e.g. some kind of index). Perhaps ClearCase has a way to delete dependencies, to avoid this problem of volatility in a central database. You might want to contact Atria. It seems that many non-Ada tools are beginning to have some kind of central database, and at least the index files of such a database would create similar problems, so I doubt if this is an Ada-only problem. -Tucker Taft stt@inmet.com Intermetrics, Inc.