Hi!
[Petter Reinholdtsen]
> Eh, don't you think a failing malloc() should be logged as well? I
> guess out of memory problems will give lots of errors elsewhere in the
> code, and it would be nice for the person trying to find the problem
> to know what is happending. I suggest logging a message like
> '[sanei_debug] malloc() failed' when this happending, in addition to
> the message itself.
Ok, I added this feature... looks reasonable to me.
> Is this the last GCC extention used in the code? I hope so. :-)
No, my backend (mustek_pp) uses some gcc-extensions :) they are soo
nice, I just had to use them... I'm using __PRETTY_FUNCTION__ to let
ASSERT() know from where it is called - do you think I should remove it?
-- jochen
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Sun Oct 22 2000 - 12:18:55 PDT