From: Ingo Schwarze <schwarze@usta.de>
To: maya@netbsd.org
Cc: tech@mandoc.bsd.lv, jmc@openbsd.org, guenther@openbsd.org
Subject: Re: -isoC-2017 patch
Date: Fri, 27 Jul 2018 16:23:26 +0200 [thread overview]
Message-ID: <20180727142326.GD18208@athene.usta.de> (raw)
In-Reply-To: <20180727134915.GB28956@homeworld.netbsd.org>
[Cc:ing two developers who know a lot about documentation and standards]
Hello Maya,
thanks for your patch!
However, i'm not sure i understand.
https://www.iso.org/standard/74528.html
seems to indicate the existence of a brand new standard called
ISO/IEC 9899:2018
Information technology -- Programming languages -- C
but i failed to find any evidence that an official standard
called ISO/IEC 9899:2017 might exist.
Can you provide a reference to such a standard?
Even if it does exist (or if you suggest s/17/18/), note that mandoc
does not aim to provide macro arguments for all the standards under
the sun. A new major revision of the C programming language is no
doubt an excellent candidate for addition, but i would still welcome
solid evidence that it will actually see substantial use in practice.
Does the NetBSD base system implement the C18 standard, and are you
going to update all the relevant NetBSD manual pages to refer to it,
where appropriate? How many manual pages, approximately, do you
expect will reference it in NetBSD in the short term?
Note the in OpenBSD, the only references even to -isoC-2011 are
in mdoc(7) and groff_mdoc(7), and
https://man.openbsd.org/?query=St%3DC11&apropos=1&manpath=NetBSD-7.1
https://man.openbsd.org/?query=St%3DC11&apropos=1&manpath=FreeBSD-11.1
only return minimal additional content, which implies to me that even
the addition of -isoC-2011 may have been premature.
Thanks again,
Ingo
maya@netbsd.org wrote on Fri, Jul 27, 2018 at 01:49:15PM +0000:
> Index: mdoc.7
> ===================================================================
> RCS file: /cvs/mandoc/mdoc.7,v
> retrieving revision 1.270
> diff -u -r1.270 mdoc.7
> --- mdoc.7 23 Oct 2017 13:54:41 -0000 1.270
> +++ mdoc.7 27 Jul 2018 13:40:36 -0000
> @@ -2451,6 +2451,11 @@
> .St -isoC-2011
> .br
> The third major version of the C language standard.
> +.Pp
> +.It \-isoC-2017
> +.St -isoC-2017
> +.br
> +The fourth major version of the C language standard.
> .El
> .It POSIX.1 before the Single UNIX Specification
> .Pp
> Index: st.in
> ===================================================================
> RCS file: /cvs/mandoc/st.in,v
> retrieving revision 1.30
> diff -u -r1.30 st.in
> --- st.in 5 Apr 2018 09:17:26 -0000 1.30
> +++ st.in 27 Jul 2018 13:40:36 -0000
> @@ -50,6 +50,7 @@
> LINE("-isoC-tcor2", "ISO/IEC 9899/TCOR2:1995 (\\(lqISO\\~C90, Technical Corrigendum 2\\(rq)")
> LINE("-isoC-99", "ISO/IEC 9899:1999 (\\(lqISO\\~C99\\(rq)")
> LINE("-isoC-2011", "ISO/IEC 9899:2011 (\\(lqISO\\~C11\\(rq)")
> +LINE("-isoC-2017", "ISO/IEC 9899:2017 (\\(lqISO\\~C17\\(rq)")
> LINE("-iso9945-1-90", "ISO/IEC 9945-1:1990 (\\(lqPOSIX.1\\(rq)")
> LINE("-iso9945-1-96", "ISO/IEC 9945-1:1996 (\\(lqPOSIX.1\\(rq)")
> LINE("-iso9945-2-93", "ISO/IEC 9945-2:1993 (\\(lqPOSIX.2\\(rq)")
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2018-07-27 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 13:49 maya
2018-07-27 14:23 ` Ingo Schwarze [this message]
2018-07-27 15:02 ` maya
2018-07-27 15:49 ` Ingo Schwarze
2018-07-27 16:11 ` maya
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=20180727142326.GD18208@athene.usta.de \
--to=schwarze@usta.de \
--cc=guenther@openbsd.org \
--cc=jmc@openbsd.org \
--cc=maya@netbsd.org \
--cc=tech@mandoc.bsd.lv \
/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).