Re: Faulty languages and Liability

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

No, its still valid to need to turn off runtime checks in *some* areas and
applications. Imagine high-speed control loops in realtime apps or
incredibly large matrix calculations that you want to finish within our
lifetimes. I'll grant you that these situations are rare in comparison to
most apps ever developed, but they do exist. If reliability is needed and
speed is an issue, the typical answer is to either analyze or extensively
test before operating without the safety net.

I agree that *most* programs should not have the checks disabled. They don't
present enough overhead to significantly impact anything & you are better
off running with them.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com


"Steve O'Neill" <oneils@gbr.msd.ray.com> wrote in message
news:3D0F2C6D.14B0380E@gbr.msd.ray.com...
>
> Because 1) there was great fear that the performance penalties might be
> too
> great for some applications and 2) some folks believed that they could
> sufficiently test the software to the point that such checks were
> unnecessary.
> In my experience neither of these are valid (at least not since the
> early 80's).