public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Joerg Schilling <schilling@fokus.fraunhofer.de>
Cc: jengelh@linux01.gwdg.de, linux-kernel@vger.kernel.org,
	drepper@redhat.com, austin-group-l@opengroup.org
Subject: Re: The naming of at()s is a difficult matter
Date: Mon, 13 Feb 2006 07:56:41 -0800	[thread overview]
Message-ID: <43F0AC39.3080007@zytor.com> (raw)
In-Reply-To: <43F09320.nailKUSI1GXEI@burner>

Joerg Schilling wrote:
> Jan Engelhardt <jengelh@linux01.gwdg.de> 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?
> 
> 
> Do you have a better proposal for naming the interfaces?
> 

Isn't it obvious?  Drop the misleading f- prefixes.

	-hpa

  reply	other threads:[~2006-02-13 15:57 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
2006-02-13 14:09   ` Joerg Schilling
2006-02-13 15:56     ` H. Peter Anvin [this message]
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=43F0AC39.3080007@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 \
    --cc=schilling@fokus.fraunhofer.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox