# Re: assert.h problems with shared libraries

From: Oliver Rauch (oliver.rauch@rauch-domain.de)
Date: Thu May 31 2001 - 14:39:01 PDT

- Next message: Nick Lamb: "Re: assert.h problems with shared libraries"
  - Previous message: Oliver Rauch: "Re: Xsane .\config errors"
  - In reply to: Henning Meier-Geinitz: "assert.h problems with shared libraries"
  - Next in thread: Nick Lamb: "Re: assert.h problems with shared libraries"
  - Reply: Nick Lamb: "Re: assert.h problems with shared libraries"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  Henning Meier-Geinitz wrote:
  > Some options: Don't use assert. Or use a local header file (lassert.h)
  > which checks for AIX and uses it's own assert if necessary. Or use a
  > #ifdef HAVE_ASSERT for every assert.
  >
  > Any good ideas?

  Hi Henning.

  An assert is an emergency stop. I think that most asserts can
  be removed without any problems (if not we would have several
  known problems).

  I think we should do this:
  1) remove assert() where it is not necessary
  2) replace an assert(a<b) by
  if (a<b) {DBG(0, "error..."); + exit or return with error code}

  Bye
  Oliver

      --
      Homepage:	http://www.rauch-domain.de
      sane-umax:	http://www.rauch-domain.de/sane-umax
      xsane:		http://www.xsane.org
      E-Mail:		mailto:Oliver.Rauch@rauch-domain.de
      --
      Source code, list archive, and docs: http://www.mostang.com/sane/
      To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

  - Next message: Nick Lamb: "Re: assert.h problems with shared libraries"
  - Previous message: Oliver Rauch: "Re: Xsane .\config errors"
  - In reply to: Henning Meier-Geinitz: "assert.h problems with shared libraries"
  - Next in thread: Nick Lamb: "Re: assert.h problems with shared libraries"
  - Reply: Nick Lamb: "Re: assert.h problems with shared libraries"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Thu May 31 2001 - 14:40:40 PDT