linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: rstanley@rsiny.com
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: Man page pre & post operators error
Date: Wed, 25 Sep 2019 21:42:36 +0200	[thread overview]
Message-ID: <3cdbcb38-734a-2b1e-ba12-f5e85a89b805@gmail.com> (raw)
In-Reply-To: <65c8c525eb718aa77816f3fe0b47e33d3504e623.camel@rsiny.com>

Hello Rick,

On 9/25/19 5:23 PM, Rick Stanley wrote:
> Hello again!
> 
> In an effort to bring the current manpage for the C operator table up
> to the current official Standard, I went back and compared the current
> manpage operator table against the C99, C11, and C17(18) Draft
> Standards documents.  I do not have access to the Official ISO C
> Standards documents.
> 
> I have attached a PDF to document my interpretation of the Standards
> against the current `man operator` manpage
> 
> In addition to the pre & postfix ++ & -- operators, I have found one
> additional change & three additions to the table.  Because of these
> appearing in 6.5.x, and A.2.1, I assume they should be included in the
> operator table.
> 
> The current table consists of 15 levels of precedence, C99 adds one new
> level and C11 adds one more.
> 
> (type) cast operator change
> 
> In the current table, the cast operator is listed on level 2 of 15
> levels, along with other operators.  In C99 this operator has been
> demoted to a new level inserted between level 2 & 3 of the current
> level, expanding the table to 16 levels of precedence.  I assume the
> associativity is also "right to left", as is level 2.
> 
> _Generic operator/keyword addition
> 
> This new operator/keyword was added in C11.  A new top level was
> created and the remainder of the table has been demoted by one level.
> 
> default operator/keyword addition
> 
> This too has been added to the new top level in C11

But, 'default' is not an operator as far as I can tell?
(It is part of the '_Generic' construct, not an operator
in its own right.)

> _Alignof operator/keyword addition
> 
> This was added to what I refer to as, the new level 3, along with other
> prefix operators. 
> 
> A new header file has been added to the C11 Standard, stdalign.h
> (7.15).  This #defines alignof to the _Alignof operator/keyword.  C11
> also #defines alignas to a related keyword, _Alignas.
> 
> No additional additions or changes to the operator table appear to have
> been made in the C17(C18) C Standard.
> 
> Please confirm my observations with the official C Standards documents.
> This is a polite request, not a demand.

I'm pretty rusty these days on interpreting grammars, but modulo
my one point above ('default' should not be there), what you say seems
plausible.

Would you be comfortable writing a patch, with a cover message 
that includes much of the text you give above?

Thanks,

Michael

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

  reply	other threads:[~2019-09-25 19:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 14:19 Man page pre & post operators error Rick Stanley
2019-09-20 17:00 ` Jakub Wilk
2019-09-22 21:01 ` Michael Kerrisk (man-pages)
2019-09-22 22:50   ` Rick Stanley
2019-09-23  7:43     ` Michael Kerrisk (man-pages)
2019-09-25 15:23     ` Rick Stanley
2019-09-25 19:42       ` Michael Kerrisk (man-pages) [this message]
2019-09-25 20:08         ` Michael Kerrisk (man-pages)
2019-09-25 22:53           ` Rick Stanley
2019-09-28 18:05         ` Manpage operator update Rick Stanley
2019-10-01 13:48         ` proposed patch to operator manpage Rick Stanley

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=3cdbcb38-734a-2b1e-ba12-f5e85a89b805@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=rstanley@rsiny.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).