pak21 at srcf.ucam.org
Sat Mar 11 11:25:34 CET 2006
On Sat, Mar 11, 2006 at 06:54:54AM +0100, Nikos Mavrogiannopoulos wrote:
> But how can you be sure that calloc() (or in that case gcry_calloc)
> will set the errno? calloc is a library call which may or may not use
> a system call. Even if it works on some systems, this is a very
> non-portable construction, which will result in no error checking in
> systems that do not set errno.
gcrypt makes certain assumptions about the system on which in it is
running. One of these is ANSI C compliance (which guarantees that
calloc() will set errno). I wouldn't exactly call that "very
"In case de curse does not succeed, dis is my lucky stake. I have killed
many vampires wit it. I call it Mr. Pointy." "You named your stake?"
"Yes." "Remind me to get you a stuffed animal."
Kendra and Buffy: Becoming, Part 1
More information about the Gcrypt-devel