Date: Sun, 2 Dec 2001 23:36:26 -0500 From: Mike Barcroft <mike@FreeBSD.ORG> To: Garance A Drosihn <drosih@rpi.edu> Cc: Bruce Evans <bde@zeta.org.au>, standards@FreeBSD.ORG Subject: Re: strerror_r() implementation Message-ID: <20011202233626.A52804@espresso.q9media.com> In-Reply-To: <p05101002b8309917497e@[128.113.24.47]>; from drosih@rpi.edu on Sun, Dec 02, 2001 at 10:12:13PM -0500 References: <20011203005459.N8502-100000@gamplex.bde.org> <p05101002b8309917497e@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
Garance A Drosihn <drosih@rpi.edu> writes: > Hmm. Should we bug someone to make that more explicit, at least for > the case of a truncated message? I just have this fear that some OS's > will implement truncated messages to always include the terminating > null, and others will prefer to put one extra byte of the error msg > into the buffer. Programs written on the OS which chooses the first > behavior might then run into trouble on the second group of OS's. Properly written applications will check the return value. It's not our job to hold the application writter's hand. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011202233626.A52804>