Re: [9fans] lpdaemon

[erik quanstrom <quanstro@quanstro.net>]

> You're absolutely correct if the length of value to be copied is not
> validated prior to the copy.  Then, an invalid page could be hit if no
> nil is present within the array or beyond.

wrong.  strncpy only copies up to the specified maximum.
the code is ugly but correct.

> To be verbose, my bypassing of strncpy is due to issues I've
> encountered in multi-threaded code.  e.g.  Don't trust libc copy
> functions in MT envs, always check post call.

this sounds like your saying that because you had trouble in
a multithreaded unix application, then without examining the
code at hand, it is pronounced to have the same issue.

that sounds like equivocation to me.  the code is correct.
and in all cases nul-terminated, and any unused bytes are
0.

i only object to strncpy because it requires extra work. seprint,
snprint are a bit heavy weight but tend to produce cleaner looking
code.  ymmv.

- erik