From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] When was #if introduced in C? (was: Re: Mac OS X is Unix)
Date: Tue, 3 Jan 2017 16:57:55 -0500 [thread overview]
Message-ID: <CAC20D2NMAfZDPs1kGLB_jUPxUWkMx75DWDwrmfafq+kewS4=9Q@mail.gmail.com> (raw)
In-Reply-To: <CAAFR5pb8d1msb+XdWPPKvAsO=eQsPgiAY8Q3cVRxoQtj_PtWkg@mail.gmail.com>
Great minds think alike.. This lines up with my memory.
On Tue, Jan 3, 2017 at 4:53 PM, Robert Swierczek <rmswierczek at gmail.com>
wrote:
> > Which makes me curious... Does anyone here happen to know when #if was
> introduced in C?
>
> From what I can gather from studying the TUHS archives, the earliest
> cpp that supports #if is in PWB:
> http://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/c/c/cpp.c
>
> Before that, the pre-processor resides within the cc.c command and #if
> is not supported:
> http://minnie.tuhs.org/cgi-bin/utree.pl?file=V6/usr/source/s1/cc.c
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170103/58878a3a/attachment.html>
next prev parent reply other threads:[~2017-01-03 21:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 20:19 [TUHS] Mac OS X is Unix Doug McIlroy
2017-01-03 21:05 ` Charles Anthony
2017-01-03 21:33 ` [TUHS] When was #if introduced in C? (was: Re: Mac OS X is Unix) Michael Kjörling
2017-01-03 21:53 ` Robert Swierczek
2017-01-03 21:57 ` Clem Cole [this message]
2017-01-03 21:56 ` Clem Cole
2017-01-03 21:35 ` [TUHS] Mac OS X is Unix Clem Cole
2017-01-03 22:10 ` Lyndon Nerenberg
2017-01-03 21:39 ` Lyndon Nerenberg
2017-01-03 22:12 ` ron minnich
2017-01-03 23:39 ` Tim Bradshaw
2017-01-04 0:12 ` ron minnich
2017-01-04 9:11 ` Tim Bradshaw
2017-01-04 10:04 ` Álvaro Jurado
2017-01-04 0:13 ` Steve Johnson
2017-01-04 3:50 ` Dan Cross
2017-01-04 12:26 ` Tim Bradshaw
2017-01-04 13:49 ` Random832
2017-01-04 15:02 ` Dan Cross
2017-01-04 17:14 ` tfb
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='CAC20D2NMAfZDPs1kGLB_jUPxUWkMx75DWDwrmfafq+kewS4=9Q@mail.gmail.com' \
--to=clemc@ccc.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).