× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I like to leave the asserts in the code.  I only use assert() in places
where I'm convinced that it can NEVER be false.   If my assumption is
wrong, I'd *much* rather have a program that crashes than one where the
bug "sneaks by" and potentially causes incorrect behavior or corrupted
production data.

Naturally, for errors that I expect *will* happen, I handle them
gracefully rather than use assert()


On Fri, 26 Sep 2003, Rich Duzenbury wrote:
>
> I'm curious, do you plan to leave the asserts in the production version of
> the code, or are you limiting them to the debug version?  In a general 'C'
> environment, I would expect the asserts to be compiled only into the debug
> version, but I haven't made any decisions about what I might do in RPG yet.
>

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.