Displaying 3 results from an estimated 3 matches for "flac_assert".
Did you mean:
flac__assert
2015 Jul 04
4
num_comments==0 and comments==0
About the removed assert in this commit: http://git.xiph.org/?p=flac.git;a=commitdiff;h=bc5113007a53be2c621d5eb5f4485eddf947ef37
It looks reasonable that if x.num_comments == 0 then x.comments is also NULL.
Otherwise there's probably a leak somewhere that should be fixed.
I found several places where the situation is reverse:
comments can be 0 but num_comments is not; IMHO it makes sense
2015 Jul 04
0
num_comments==0 and comments==0
What is the advantage of removing an assert? - even FLAC_ASSERT()
My understanding is that assert() is only compiled into the code with Debug builds, whereas with a Release build the assert() macro will generate no code at all. In other words, when you build for testing, the assert is there, but when you build the fully optimized version the assert will be rem...
2004 Sep 10
2
FLAC/assert.h overwrites /usr/include/assert.h?
...cially because of the name?
Josh
--- Kyle Sallee <cromwell@kublai.com> wrote:
> It's installation overwrites /usr/include/assert.h
> which is isntalled by glibc, thus causing many other programs
> to fail during compilation. Perhaps flac's assert.h could
> be renamed to flac_assert.h to avoid the endless trouble
> caused by overwritting the assert.h installed by glibc, please?
__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com