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.1 required=5.0 tests=BAYES_05,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public X-Google-Thread: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public From: rrg@funsys.se (Robin Rosenberg) Subject: Re: OO, C++, and something much better! Date: 1997/02/08 Message-ID: #1/1 X-Deja-AN: 217502631 sender: usenet@funsys.funsys.se references: <32E999AE.2F68@parcplace.com> followup-to: comp.object organization: Enator Objective Management AB newsgroups: comp.object,comp.lang.c++,comp.lang.ada,comp.lang.smalltalk,comp.lang.eiffel Date: 1997-02-08T00:00:00+00:00 List-Id: tkc@bmi.net (Travis Griggs) writes: > > Of course, the developer opened his debugger, found the offending > message send, fixed the method, and restarted, right? Meanwhile, the > statically typed developer still didn't have the feature. :) In SparcWorks/C++ you can inspect the problem in the debugger, edit the offending code and resume execution at some appropriate point int the program. So this can be done in a statically typed/compiled language. -- Robin Rosenberg, | Voice: +46-8-7036200 | "Any opinions are my own, etc. etc." Enator Objective | Fax: (+46-8-7036283)| Management AB | Mail: rrg@funsys.se |