[2nd try, the first message went apparently lost] Hi all: I have noticed that the assert() calls inside the libpulse client library are enabled by default. I would expect asserts to be disabled in release builds, via the NDEBUG macro or similar compile-time switch. What's the common practice for asserts in the OSS world in this kind of libraries? I've seen in other projects a "--disable-assert" argument to the ./configure script. Would that (or --enable-assert) be an option to consider? Thanks, Ruben __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verf?gt ?ber einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
