On Tue, Jan 11, 2000 at 12:49:32PM -0600, Richard Seaman, Jr. wrote:
> On Tue, Jan 11, 2000 at 10:35:27AM -0800, Jason Evans wrote:
> > The naming
> > approach I'm taking is:
> >
> > fwrite() <-- Alternate entry point that is used externally unless
> > another library overrides it.
> > _libc_fwrite() <-- `_libc_' prefix. Alternate entry point for internal
> > library use.
> > __fwrite() <-- `__' prefix. Actual name.
> >
> > The reason for a prefix of `__' instead of `_' in the actual name case is
> > that using only one underscore would be ambiguous at least in the cases of
> > setjmp()/_setjmp() and longjmp()/_longjmp().
>
> FYI, the actual name with a single '_' is already defined for syscalls via
> SYS.h. Aliasing '__sycall' to '_syscall' is ok, I assume. Or, are you planning
> on replacing the '_syscall's? Setjmp/_setjmp are libc calls but not syscalls.
> I'm under the impression that linux glibc uses both single and double underscore
> symbols, but I don't recall exactly what distinction they make between the two.
It would be more consistent to change to `__' for syscalls, but I was
planning on leaving the syscalls with `_', and adding `__' aliases, for
fear that changing it would violate some "law of libc".
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
