Article View: comp.lang.lisp.mcl
Article #664Re: Re2: Mother ship App.(flame)
From: language
Date: Mon, 25 Jan 1993 19:35
Date: Mon, 25 Jan 1993 19:35
16 lines
1235 bytes
1235 bytes
> The "problem" of buggy MCL applications can be viewed from another
> angle: Most of those buggy MCL applications wouldn't have been
> completed at all if they had been implemented in another language,
> and they most certainly would not have been less buggy at the
> same level of fuctionality.
well, I'm not really talking about 'buggy' in the sense that there
are a lot of lisp exceptions. lisp has a wonderful debugging environment
that works well inside of mcl. What I am taling about are the apparant
mystery crashes that happen for no apparant reason, why a program
crashes on one machine and not another, the mouse freezing, why
version 2.0 crashes every time with the even-better-buss-error init
distributed at ftp.apple.com. unexplained mouse freezing, that sort of
thing. These things simply should not happen!
-john
Technical Details
Message-ID:
<9301251935.AA08196@waskesiu.USask.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!olivea!apple!cambridge.apple.com!language@skdad.usask.caShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!apple!cambridge.apple.com!language@skdad.usask.ca From: language@skdad.usask.ca Newsgroups: comp.lang.lisp.mcl Subject: Re: Re2: Mother ship App.(flame) Message-ID: <9301251935.AA08196@waskesiu.USask.ca> Date: 25 Jan 93 19:35:15 GMT Sender: owner-info-mcl@cambridge.apple.com Lines: 16 Approved: comp.lang.lisp.mcl@Cambridge.Apple.C0M