- 2008.12.18 04:56 "[Tiff] tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
-
2008.12.18 21:56 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
-
2008.12.18 19:04 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
- 2008.12.18 19:18 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Edward Lam
-
2008.12.18 19:20 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
-
2008.12.18 19:28 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
- 2008.12.18 19:35 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
- 2008.12.18 20:42 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
-
2008.12.18 19:28 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
- 2008.12.18 22:05 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
- 2008.12.21 16:03 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Jay Berkenbilt
-
2008.12.18 19:04 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
-
2009.01.21 04:07 "[Tiff] libtiff 4.0.0beta3", by Frank Warmerdam
-
2009.01.21 21:11 "Re: [Tiff] libtiff 4.0.0beta3", by Edward Lam
-
2009.01.22 16:23 "Re: [Tiff] libtiff 4.0.0beta3", by Edward Lam
- 2009.01.22 16:31 "Re: [Tiff] libtiff 4.0.0beta3", by Bob Friesenhahn
- 2009.01.22 17:00 "Re: [Tiff] libtiff 4.0.0beta3", by Bob Friesenhahn
- 2009.01.22 19:38 "Re: [Tiff] libtiff 4.0.0beta3", by Frank Warmerdam
-
2009.01.22 16:23 "Re: [Tiff] libtiff 4.0.0beta3", by Edward Lam
-
2009.01.21 21:11 "Re: [Tiff] libtiff 4.0.0beta3", by Edward Lam
- 2009.01.22 07:15 "[Tiff] Bugzilla not available?", by Rob Eisink
-
2009.02.05 18:38 "[Tiff] assertions, and building with DEBUG/NDEBUG", by Frank Warmerdam
- 2009.02.05 19:04 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by Edward Lam
-
2009.02.05 19:13 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by Bob Friesenhahn
- 2009.02.05 19:26 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by Frank Warmerdam
- 2009.02.06 10:07 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by
- 2009.02.06 10:44 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by
- 2009.02.26 22:44 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by
- 2009.02.07 14:10 "Re: [Tiff] The OJPEG bug 1996", by
2009.02.05 20:00 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by Bob Friesenhahn
I have not heard of a build production process for open-source based systems which intentionally disables assertions. More than likely they are disabled in quite a few closed-source applications.
It has always been my practice and assumption that assertions should be disabled in production software where performance and appropriate error handling is considered important.
Perhaps open-sourced operating systems are not really production software. :-)
My own software contains quite a lot of assertion statements but the performance boost from removing them was only a few percent. Quite a lot of the influence on performance is if the values checked will be immediately used or not. If the values will be immediately used then the assertion is almost free since the first access to the value is most of the cost. If the value is off in some data structure which is otherwise rarely used, then the cost may be rather high.
Regardless, I think that it should be up to the person building libtiff to decide if NDEBUG should be applied, and that it should not be the default.
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/