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: fac41,2c6139ce13be9980 X-Google-Attributes: gidfac41,public X-Google-Thread: f43e6,2c6139ce13be9980 X-Google-Attributes: gidf43e6,public X-Google-Thread: 1108a1,2c6139ce13be9980 X-Google-Attributes: gid1108a1,public X-Google-Thread: 103376,3d3f20d31be1c33a X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Design by Contract Date: 1997/08/28 Message-ID: #1/1 X-Deja-AN: 268801801 References: <33E9ADE9.4709@flash.net> <34023BC4.2781E494@eiffel.com> <3402d123.0@news.uni-ulm.de> <3402DA6A.C4444E46@calfp.co.uk> <3402e51d.0@news.uni-ulm.de> <3402E8C9.3384D976@calfp.co.uk> <34050F3C.5A3A@invest.amp.com.au> Organization: New York University Newsgroups: comp.object,comp.software-eng,comp.lang.ada,comp.lang.eiffel Date: 1997-08-28T00:00:00+00:00 List-Id: <> The reason I disagree is that it makes configuration management much more complex. Obviously changing a spec is a much different activity than changing a body. The set of people who are allowed to make the change will typically be different, and the procedures to be followed to allow the change to be made will most certainly be different. By having separate files, one can control CM at the file level, which is the natural way of doing things. I don't know Eiffel well enough to know how easy it would be to make the CM system aware of *what kind* of change you were making, from what I know of Eiffel, it sounds difficult.