Subject: Re: Syscall and syscall versioning documentation
To: None <tech-kern@netbsd.org>
From: Christos Zoulas <christos@astron.com>
List: tech-kern
Date: 11/22/2006 19:52:17
In article <20061121221624.GA698@beta.martani.repy.czf>,
Pavel Cahyna <pavel@netbsd.org> wrote:
>>
>> Thanks!
>>
>> 1. Why not use ansi prototypes to simplify the formatting?
>
>I've used Docbook prototypes. If another formatting is desired, it should
>be done by altering the templates.
I don't know, I would think that the ANSI ones would be prettier.
>> 3. In 3.2.6, mention that we usually implement the older version of the
>> syscall in libc so that we can provide binary compatibility for
>> dynamically linked libraries without needing the kernel support.
>
>This was already there.
ok
>> Also mention that we don't litter the code with compat defines,
>> but we put stuff in lib/libc/compat or sys/compat.
>
>This too.
ok.
>> Mention how __RENAME() works and the __LIBC12_SOURCE__ define.
>
>I've mentioned what __RENAME does but now how it works, because its user
>should not care.
I meant document that the __LIBC12_SOURCE__ symbol is used to choose
when to rename functions for libc.so.12 compatibility, and that the
__RENAME() macro is used to rename symbols.
christos