From: Charlie Lin <charlielin65@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 5th Edition
Date: Wed, 16 Nov 2016 20:14:12 -0500 [thread overview]
Message-ID: <CAJvBL5yA5N_Qkyes4Fcn_=qKE418EGcL6YDSoD7FE_YtATte5Q@mail.gmail.com> (raw)
In-Reply-To: <CAPd04b7siYsma89cLNM_neMmjrxpL6o87eZb2ibCTGCOmQJxQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
I have the ANSI X3.159-1989 (C89), the ISO/IEC 9989:1990 (C90) (ANSI
version) and ISO/IEC 9989:1999 (C99).
The first one I found it at the National Technical Reports Library. The
other two I do not know where I obtained them but I know they are on the
Internet, as final standards, not drafts.
On Nov 16, 2016 7:35 PM, "James A. Robinson" <jimr@highwire.org> wrote:
> On Wed, Nov 16, 2016 at 3:54 PM Chris McGee <newton688@gmail.com> wrote:
>
>> A C compiler that supports the latest spec would be nice as long as it
>> doesn't sacrifice compile times. I like how quickly the system can
>> recompile itself. Maybe extend pcc to include new features?
>>
>
> I'll admit to never having paid much attention to the changing
> specification for C. By latest spec you're referring to C11? I recall a
> coworker pointing me at http://www.tinycc.org/ awhile ago, and looking at
> the page today it says it mostly implements the previous C99 specification
>
> It claims to be small, mostly compliant to C99 ("Currently missing items
> are: complex and imaginary numbers and variable length arrays."), and fast.
> But it isn't under development by the original author any more.
>
> Jim
>
>
[-- Attachment #2: Type: text/html, Size: 2138 bytes --]
next prev parent reply other threads:[~2016-11-17 1:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 22:27 Charlie Lin
2016-11-16 22:43 ` Stanley Lieber
2016-11-16 22:44 ` Ole-Hjalmar Kristensen
2016-11-16 23:53 ` Chris McGee
2016-11-17 0:34 ` James A. Robinson
2016-11-17 1:14 ` Charlie Lin [this message]
2016-11-17 16:16 ` Dave MacFarlane
2016-11-17 17:50 ` Ori Bernstein
2016-11-17 20:29 ` Chris McGee
2016-11-17 20:32 ` Ori Bernstein
2016-11-17 20:31 ` Chris McGee
2016-11-17 0:21 ` Charlie Lin
2016-11-17 0:30 ` Kurt H Maier
2016-11-18 19:54 ` Charlie Lin
2016-11-18 19:57 ` Charlie Lin
2016-11-18 19:58 ` Charlie Lin
2016-11-18 22:26 ` hiro
2016-11-18 22:28 ` hiro
2016-11-19 16:57 ` cinap_lenrek
2016-11-19 18:42 ` Steve Simon
[not found] ` <CAEVxPTMKBpWFEGr-k1diNa2BVgCjsL1g-OPZdhn9LmEn3uLB5g@mail.gmail.com>
[not found] ` <CAEVxPTN_KZn_4+s1xr-uiDzEY72wf2AtrXYN_FDgdaPbyqpLbw@mail.gmail.com>
2016-11-18 20:07 ` Jules Merit
2016-11-17 0:55 ` Charlie Lin
2016-11-17 1:02 ` Stanley Lieber
2016-11-17 1:18 ` Kurt H Maier
2016-11-19 22:27 ` David Arnold
2016-11-20 2:39 ` hiro
2016-11-20 4:26 ` Ryan Gonzalez
2016-11-20 6:22 ` Kurt H Maier
2016-11-20 6:54 ` James A. Robinson
2016-11-20 9:44 ` hiro
2016-11-21 2:19 ` Wes Kussmaul
2016-11-21 8:02 ` hiro
2016-11-21 8:02 ` Kurt H Maier
2016-11-21 8:46 ` Sigrid Haflinadóttir
2016-11-21 15:08 ` Wes Kussmaul
2016-11-21 15:42 ` Chris McGee
2016-11-19 20:19 ` Charlie Lin
2016-11-19 20:37 ` Charlie Lin
2016-11-19 21:51 ` Steve Simon
2016-11-19 22:27 ` Stanley Lieber
2016-11-20 15:23 ` Chris McGee
2016-11-20 18:09 ` hiro
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='CAJvBL5yA5N_Qkyes4Fcn_=qKE418EGcL6YDSoD7FE_YtATte5Q@mail.gmail.com' \
--to=charlielin65@gmail.com \
--cc=9fans@9fans.net \
/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).