Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cmcl2!esquire!yost From: yost@esquire.UUCP (David A. Yost) Newsgroups: comp.lang.eiffel Subject: Re: Eiffel Automatic Configuration Management Keywords: es Message-ID: <1352@esquire.UUCP> Date: 14 Aug 89 13:46:11 GMT References: <1752@eric.mpr.ca> Reply-To: yost@esquire.UUCP (David A. Yost) Organization: DP&W, New York, NY Lines: 15 In article <1752@eric.mpr.ca> murphy@eric.mpr.ca (Gail Murphy) writes: >I have found that "es" is great for small Eiffel systems, but once >a system starts to become large, the time spent in reanalyzing >the system for small bug fixes (ie. forget to define an integer, misspell >variable name, only require re-link due to change in external C object) >is not acceptable. Are you saying that every time you run es it reads all the program text of all the classes in the program to determine what to do? Or is it that there is no way to tell es how the classes depend on external C code? --dave yost