All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Ping: Consistent parameter names
Date: Sat, 22 May 2021 00:19:47 +0200	[thread overview]
Message-ID: <e7814c4e-fcd8-8e7e-742a-f35cda31848a@gmail.com> (raw)
In-Reply-To: <548683d1-4a39-5f1f-2459-36c95844a0a8@gmail.com>

Ping.

On 3/4/21 3:50 PM, Alejandro Colomar (man-pages) wrote:
> Hello Michael,
> 
> 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 consistent (>90% use 'stream'):
>      - stream
>      - streamp
>      - s
>      - fp
>      - file
>      - filehandle
>      - A few others in specific cases
> 
> Also for strings, there are
>     - s
>     - str
>     - string
>     - maybe others
> 
> There are probably other cases with the same problem.
> I think these parameters should have a more consistent naming.
> But which names should we use?
> 
> I tend to use short names such as fname, fd, s, ...
> but I don't know if you may prefer longer names for documentation purposes.
> 
> What would you do about it?
> 
> Thanks,
> 
> Alex
> 

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

      reply	other threads:[~2021-05-21 22:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 14:50 Consistent parameter names Alejandro Colomar (man-pages)
2021-05-21 22:19 ` Alejandro Colomar (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=e7814c4e-fcd8-8e7e-742a-f35cda31848a@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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.