Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!rutgers!aramis.rutgers.edu!topaz.rutgers.edu!elkins From: elkins@topaz.rutgers.edu (George Elkins) Newsgroups: comp.lang.eiffel Subject: Re: Eiffel and the NeXT Keywords: Eiffel, NeXT Message-ID: Date: 20 Dec 89 16:22:13 GMT References: <6058@mentor.cc.purdue.edu> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 16 > ... but Eiffel provides all the qualities > necessary to intense development of well-defined (ANSI-C or C++ > code is not well defined) and reusable class-libraries neccessary > to the NeXT. I agree. When I last programmed in Eiffel, it seemed that about 60% of the code I ended up using was inherited from class libraries or demo code. Application development, as a result, was extremely fast (especially considering that I had never done any Eiffel programming or OOP before this). As a result of this experience, I would take NeXT more seriously if an Eiffel compiler and Eiffel class libraries were available. Is ISE considering this possibility? George Elkins