Milter-greylist

Greg Troxel wrote:
 > 
 >   I was just wondering because bzero()'s purpose is
 >   specifically to fill an area of memory with zeros.
 > 
 >   It saves a few bytes in the binary and a few cycles
 >   during execution, but it's not significant.  (It's
 >   even possible that the compiler optimizes a call
 >   to memset(..., 0, ...) with constant 0 to bzero(),
 >   but I'm not sure if common compilers are that smart.)
 > 
 > IIRC basically bzero is a BSD thing, and memset is C99, and I think nthe
 > NetBSD codebase has moved to memset and memcp from bzero and bcopy.

bzero() is POSIX, so portability should not be a concern.

Don't get me wrong, I'm not saying the code should be
changed.  I was really just wondering.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Gesch\ufffdftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M\ufffdn-
chen, HRB 125758,  Gesch\ufffdftsf\ufffdhrer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"I have stopped reading Stephen King novels.
Now I just read C code instead."
        -- Richard A. O'Keefe