All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH 00/20] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 1)
Date: Wed, 3 Mar 2021 23:14:58 +0100	[thread overview]
Message-ID: <fe535a38-d2da-b5a9-06b2-96adfa54d3de@gmail.com> (raw)
In-Reply-To: <20210224144310.140649-1-alx.manpages@gmail.com>

Hello Alex,

On 2/24/21 3:42 PM, Alejandro Colomar wrote:
> Hi Michael,
> 
> This are the first pages of man3 with 'restrict'.
> I'm sending you these already, becuase otherwise I'd accumulate
> too many patches in the end.

Thanks. I have applied all of these.

> I have fixed from the first page until ftw.3.
> 
> Spin off:
> 	I found different terms for parameters that refer to a same thing
> 	in different functions (usually a '[const] char *'):
> 	 - filename
> 	 - file
> 	 - path
> 	 - pathname
> 	 - Maybe others; I don't know
> 
> 	For 'FILE *' we have more or less the same,
> 	although this one is much more standard (>90% use 'stream'):
> 	 - stream
> 	 - streamp
> 	 - s
> 	 - fp
> 	 - file
> 	 - filehandle
> 	 - A few others in specific cases
> 
> 	What would you do about it?
I think it would be best to start a new thread for this...

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      parent reply	other threads:[~2021-03-04  0:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 14:42 [PATCH 00/20] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 1) Alejandro Colomar
2021-02-24 14:42 ` [PATCH 01/20] argz_add.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-02-24 14:42 ` [PATCH 02/20] asprintf.3: " Alejandro Colomar
2021-02-24 14:42 ` [PATCH 03/20] memccpy.3: " Alejandro Colomar
2021-02-24 14:42 ` [PATCH 04/20] memcpy.3: " Alejandro Colomar
2021-02-24 14:42 ` [PATCH 05/20] crypt.3: " Alejandro Colomar
2021-02-24 14:42 ` [PATCH 06/20] ctime.3: " Alejandro Colomar
2021-02-24 14:42 ` [PATCH 07/20] " Alejandro Colomar
2021-02-24 14:42 ` [PATCH 08/20] dlinfo.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 09/20] dlsym.3: SYNOPSIS: Use 'restrict' in prototypes; add missing 'const' too Alejandro Colomar
2021-02-24 14:43 ` [PATCH 10/20] drand48_r.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-02-24 14:43 ` [PATCH 11/20] ecvt_r.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 12/20] ecvt.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 13/20] envz_add.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 14/20] fgetc.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 15/20] fgetws.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 16/20] fopencookie.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 17/20] fopen.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 18/20] fputws.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 19/20] fread.3: " Alejandro Colomar
2021-02-24 14:43 ` [PATCH 20/20] fseek.3: " Alejandro Colomar
2021-03-03 22:14 ` Michael Kerrisk (man-pages) [this message]

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=fe535a38-d2da-b5a9-06b2-96adfa54d3de@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=xypron.glpk@gmx.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 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.