svn commit: r192398 - in head/usr.bin: . perror

Gabor Kovesdan gabor at
Fri May 22 10:36:57 UTC 2009

Bruce Evans escribió:
> On Thu, 21 May 2009, M. Warner Losh wrote:
>> In message: <20090521110115.GA50355 at>
>>            Alexey Dokuchaev <danfe at> writes:
>> : > Given how easy it is to "grep <<errno>> /usr/include/sys/errno.h" or
>> : > perl -e '$! = <<errno>>; print "$!\n";'
>> : > I'm not sure of the utility of this tool.
>> :
>> : User scripts should not depend on presence of system include files.
>> : Now, just to mention, Nick's suggestion about dropping extra noise
>> : 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.
Our man page toolset doesn't really support localization. I haven't done 
big investigations but I remember that lack of ISO8859-2 support 
prevented us from translating man pages into Hungarian. Beside this, it 
isn't a flexible way of listing the error messages there because you 
have to explicitly list them or make some magic to generate the man 
page. But what if a specific translation changes? What if a new 
translation is added? One will have to keep these in sync then. While 
retrieving those messages from C code is trivial and no such 
considerations are needed, so I vote for the perror utility.

Gabor Kovesdan
FreeBSD Volunteer

EMAIL: gabor at .:|:. gabor at
WEB: .:|:.

More information about the svn-src-all mailing list