Date: Fri, 22 May 2009 11:41:38 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Bruce Evans <brde@optusnet.com.au> Cc: unixmania@gmail.com, danfe@freebsd.org, src-committers@freebsd.org, peterjeremy@optushome.com.au, svn-src-all@freebsd.org, stas@freebsd.org, gnn@freebsd.org, svn-src-head@freebsd.org, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: svn commit: r192398 - in head/usr.bin: . perror Message-ID: <alpine.BSF.2.00.0905221139020.17322@fledge.watson.org> In-Reply-To: <20090522195717.U22330@delplex.bde.org> References: <e71790db0905201558u1c8e3e90n1fbbfc4011e22909@mail.gmail.com> <20090521132404.cc5be268.stas@FreeBSD.org> <20090521110115.GA50355@FreeBSD.org> <20090521.085256.-1989816394.imp@bsdimp.com> <20090522195717.U22330@delplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 22 May 2009, Bruce Evans wrote:
>> : actually good one.
>>
>> There's also internationalization that actually happens too, right? That
>> doesn't happen with grep..
>
> What about with "man errno". Man pages are slightly more likely to be
> present than application (not system) include files, and man should support
> localization. It gives more noise than grepping an include file, but the
> noise might be signal and can be filtered.
For me, at least, a simple text -> errno name ("EPERM") would go a long way,
since they aren't internationalized strings, and are therefore usable in
scripts in useful ways. On the topic of man pages though -- I was interested
to see that Mac OS X does not ship with an errno(2), despite shipping with a
BSD-derived errno.h.
Robert N M Watson
Computer Laboratory
University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0905221139020.17322>