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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public X-Google-Thread: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public From: Eirik Mangseth Subject: Re: What is wrong with OO ? Date: 1997/01/17 Message-ID: <32DFEF45.1B3B@online.no>#1/1 X-Deja-AN: 210499934 references: <5bifbqINNgh3@maz4.sma.ch> <32DCD7E1.5242@ehs.ericsson.se> <5bo7nq$b8b@news.istar.ca> content-type: text/plain; charset=us-ascii organization: United Consultants A/S mime-version: 1.0 reply-to: emangset@online.no newsgroups: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.object,comp.software-eng x-mailer: Mozilla 3.0Gold (Win95; I) Date: 1997-01-17T00:00:00+00:00 List-Id: Tom Bushell wrote: > > On Wed, 15 Jan 1997 14:13:05 +0100, Jonas Nygren > wrote: > > > > >I remember I had a GUI app on my MacPlus where the cycle 'stop testing - > >fix something small - compile - link - ready to test again' was under 30 > >secs, > >with a M68000 ~7 MHz!! > > 30 seconds seems like a lifetime after you get used to RAD languages > like Smalltalk, VB, or Prograph. Turnaround is instant, and you can > usually fix the program _while it is running_ - no need to even > restart. This allows the programmer to much more easily stay in an > immersive state of "flow", and probably accounts for a large portion > of the productivity gains possible with these language/environments. > > As I believe someone else already pointed out, the C++ compiler > convention of creating an optimized, native code, standalone > executable file on disk is ass backwards - this should be a batch > operation that is performed once to create the production version of > the program. The rest of the time, it is much more important to allow > rapid turnaround for modifications, at the expense of execution speed > if necessary. > > I was impressed by the description of Eiffel's approach to this - > sounds exactly right to me. Check out Bertrand Meyer's article regarding the work ISE is doing on concurrency in Eiffel. It's a gem and Mr. Meyer is just impressive. (Just hope he signs my copy of the OOSC 2nd ed. book) > > -Tom > > ---------------------------------------------------------- > Tom Bushell * Custom Software Development > Telekinetics * Process Improvement Consulting > 2653 Highway 202 * Technical Writing > RR#1, Elmsdale, NS > B0N 1M0 > (902)632-2772 Email: tbushell@fox.nstn.ns.ca > ---------------------------------------------------------- Eirik M. /Eirik Mangseth United Consultants A/S, Oslo Office, Norway ema@uc-unitedconsultants.com "Quality Software Through Quality People" (TM) emangset@online.no /