Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!rochester!cornell!uw-beaver!tektronix!uunet!mcvax!ace!konijn From: konijn@ace.UUCP (Erik van Konijnenburg) Newsgroups: comp.lang.modula2 Subject: Re: Modula 2 for the Sun 3 - summary of responses Message-ID: <549@ace.UUCP> Date: 22 Jul 88 11:42:54 GMT Sender: news@ace.UUCP Reply-To: konijn@ace.UUCP (Erik van Konijnenburg) Organization: ACE Associated Computer Experts bv, Amsterdam Lines: 33 Hi. In his summary of responses, writes: > One point that mystified me is why Modula should need special make and version > control gubbins, as Sun, ACE and Oregon all provide. Why can't the general > purpose ones - SCCS, nmake, and friends - hack it? The general purpose ones can, but they need some help. As an example, you would not want to have to edit your makefile every time you change an import dependency between modules, so we added a tool that automatically adds the import dependencies to an ordinary makefile. In the area of source code version control, SCCS does just fine as the bottom layer of CADESE, an integrated source and distribution management system. There is nothing language specific here, so we don't package CADESE with the Modula-2 compiler. Source code version control does not protect you from accidentally using the compiled version of an implementation module in combination with a definition module that has been radically altered after the implementation was compiled, so it is up to the Modula-2 compiler to give a warning if this happens. To do this, you need a time stamp in the compiled objects, but that is all a Modula-2 compiler needs to know about version control. Erik. --------- Erik van Konijnenburg email: ACE Associated Computer Experts bv ...!mcvax!ace!konijn van Eeghenstraat 100 tel: +31 20 6646416 1071 GL Amsterdam fax: +31 20 750389 The Netherlands tx: 11702 (ace nl)