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,a7e399a115a66840
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: new programmer wondering what to learn
Date: 1997/05/30
Message-ID: <dewar.865032799@merv>#1/1
X-Deja-AN: 245074703
References: <97053009383440@psavax.pwfl.com>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-05-30T00:00:00+00:00
List-Id: <comp.lang.ada>


Marin said

<<    O.K. I see the point. If two versions of a file differ in
    specification, Ada is going to warn you about it. The compilation
    system by design has to do some sort of time stamping or version
    checking to know what's out of date. I can see how that can be
    construed as "Configuration Management".>>

Well I think ensuring consistent builds is indeed *one* of the functions
of a CM system (let's put it this way, any CM system that cannot provide
this assurance, say when working with C++ programs, is missing a critical
capability). But no one would say that this is all CM is about!