compat/unsafe.h

Stumbled over compat/unsafe.h again when trying to compile trunk after
the purge merge.

Imho these rules in compat/unsafe.h should be dropped, replaced by
coding standards for the different sections and auditing.

- The rules originally come from lazyness in Squid-2 where we did not
want to check return code of malloc() or is data had been allocated
before free().
- The way they are implemented (#define) causes issues with perfectly
valid code such as system headers..
- these rules makes it harder to integrate other code.

Regards
Henrik
Received on Fri Aug 20 2010 - 02:52:58 MDT