From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"'austin-group-l@opengroup.org'" <austin-group-l@opengroup.org>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: The naming of at()s is a difficult matter
Date: Sun, 12 Feb 2006 09:42:36 -0800 [thread overview]
Message-ID: <43EF738C.2090109@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0602121137090.25363@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>>I have noticed that the new ...at() system calls are named in what
>>appears to be a completely haphazard fashion. In Unix system calls,
>>an f- prefix means it operates on a file descriptor; the -at suffix (a
>>prefix would have been more consistent, but oh well) similarly
>>indicates it operates on a (directory fd, pathname) pair.
>
> shmat operates on dirfd/pathname?
>
Convention collision. They unfortunately happen (yet another reason the
-at convention was ill choosen); another pretty bad clash is the f-
prefix for use on file descriptors versus use on FILE *...
-hpa
next prev parent reply other threads:[~2006-02-12 17:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 3:33 The naming of at()s is a difficult matter H. Peter Anvin
2006-02-12 10:37 ` Jan Engelhardt
2006-02-12 17:42 ` H. Peter Anvin [this message]
2006-02-13 14:09 ` Joerg Schilling
2006-02-13 15:56 ` H. Peter Anvin
2006-02-14 8:17 ` Jan Engelhardt
2006-02-14 15:09 ` Joerg Schilling
2006-02-14 15:21 ` H. Peter Anvin
2006-02-14 16:13 ` Matthew Frost
2006-02-14 17:00 ` Joerg Schilling
2006-02-14 17:35 ` H. Peter Anvin
2006-02-14 18:07 ` Jan Engelhardt
2006-02-14 18:12 ` H. Peter Anvin
2006-02-14 18:17 ` Jan Engelhardt
2006-02-14 18:53 ` Joerg Schilling
2006-02-14 18:51 ` Joerg Schilling
2006-02-12 14:41 ` Jim Meyering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43EF738C.2090109@zytor.com \
--to=hpa@zytor.com \
--cc=austin-group-l@opengroup.org \
--cc=drepper@redhat.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.