public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: der Mouse <mouse-QYwwddsQ6tkEPrhfXw3Q4tGeqqvjHH9B@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: lseek(2) BSD buglet
Date: Sat, 14 Aug 2010 10:09:41 -0400 (EDT)	[thread overview]
Message-ID: <201008141409.KAA00313@Sparkle.Rodents-Montreal.ORG> (raw)
In-Reply-To: <20100814094840.GA6217-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

>> lseek(2) (noticed on 3.23, 3.25 has similar wording) says, in part,

>>        SVr1-3 returns long instead of off_t, BSD returns int.

> I think removing it is fine.  Historical SysV and BSD behaviour might
> have been interesting in the early 90s, but these days it's something
> for a history book and not a manual page.

Sounds like a reasonable point of view to me.

However, since the manpages are also one of the places people go when
trying to figure out old code, I'd probably not delete it entirely but
instead replace it with something alojng the lines of

	Hisorical practice has varied, but modern systems uniformly use
	off_t.

But, really, even that may be more than is worth bothering with; it's
been a long time since lseek returning non-off_t mattered to anyone but
hardcore retrocomputing geeks.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse-NcIlfYlhY41Ekk/fuQG8RGD2FQJk+8+b@public.gmane.org
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-08-14 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 18:13 lseek(2) BSD buglet der Mouse
     [not found] ` <201008111813.OAA03192-23rEAq0nvmRBjDB12xDq2QQ+uF9fDdDi0Z6qq+Mcf0E@public.gmane.org>
2010-08-14  9:48   ` Christoph Hellwig
     [not found]     ` <20100814094840.GA6217-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2010-08-14 14:09       ` der Mouse [this message]
     [not found]         ` <201008141409.KAA00313-23rEAq0nvmRBjDB12xDq2QQ+uF9fDdDi0Z6qq+Mcf0E@public.gmane.org>
2010-09-11  4:18           ` Michael Kerrisk

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=201008141409.KAA00313@Sparkle.Rodents-Montreal.ORG \
    --to=mouse-qywwddsq6tkeprhfxw3q4tgeqqvjhh9b@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox