Re: The naming of at()s is a difficult matter

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • The naming of at()s is a difficult matter
    • From: "H. Peter Anvin" <[email protected]>
  • Re: The naming of at()s is a difficult matter
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: [PATCH 5/5] dasd: kill dynamic ioctl registration
• Next by Date: [RFC: 2.6 patch] remove the CONFIG_CC_ALIGN_* options
• Previous by thread: Re: The naming of at()s is a difficult matter
• Next by thread: Re: The naming of at()s is a difficult matter
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]