From: Jason McIntyre <jmc@kerhand.co.uk>
To: tech@mandoc.bsd.lv
Subject: [jmc@kerhand.co.uk: Re: -isoC-2017 patch]
Date: Sun, 29 Jul 2018 16:04:40 +0100 [thread overview]
Message-ID: <20180729150439.GA10187@harkle> (raw)
resending now ingo agrees i may spam you all!
jmc
----- Forwarded message from Jason McIntyre <jmc@kerhand.co.uk> -----
Date: Sat, 28 Jul 2018 18:51:20 +0100
From: Jason McIntyre <jmc@kerhand.co.uk>
To: maya@netbsd.org
Cc: tech@mandoc.bsd.lv, guenther@openbsd.org
Subject: Re: -isoC-2017 patch
On Fri, Jul 27, 2018 at 04:11:46PM +0000, maya@netbsd.org wrote:
> On Fri, Jul 27, 2018 at 05:49:44PM +0200, Ingo Schwarze wrote:
> > > like C11
> >
> > After looking at the draft, it seems to me that there will likely
> > even be fewer references to C18 than to C11, given that C11 did
> > define a small number of new features, which at least in theory
> > might get implemented and documented.
>
> Off the top of my head, C11 adds atomics, generics and threads. it's
> pretty big.
i kind of agree with ingo's plan to see if it will be used by more than
just two or three pages before adding a macro.
jmc
----- End forwarded message -----
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
reply other threads:[~2018-07-29 15:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180729150439.GA10187@harkle \
--to=jmc@kerhand.co.uk \
--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).