public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Joerg Schilling <schilling@fokus.fraunhofer.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: Tue, 14 Feb 2006 10:12:20 -0800	[thread overview]
Message-ID: <43F21D84.8010907@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0602141907030.32490@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
>>>>Do you have a better proposal for naming the interfaces?
>>>
>>>chownfn maybe. (fd + name)
>>
>>I am not shure if this would match the rules from the Opengroup.
>>Solaris has these interfaces since at least 5 years.
> 
> This is not the cdrecord thread so Solaris is a no-go in this very one.
> 

FWIW, I think the -at() suffix is just fine, and well established by now 
(yes, there is shmat, but the SysV shared memory interfaces are bizarre 
to begin with -- hence POSIX shared memory which has real names.)

What I object to is the random, meaningless and misleading application 
of the f- suffix.

	-hpa

  reply	other threads:[~2006-02-14 18:12 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
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 [this message]
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=43F21D84.8010907@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