The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dwalker@doomd.net (Derrik Walker v2.0)
Subject: [TUHS] K&R C on a modern Linux box? ( was Re: I swear! I rtfm'ed )
Date: Wed, 31 Dec 2014 02:52:46 -0500	[thread overview]
Message-ID: <1420012366.2068.13.camel@doomd.net> (raw)
In-Reply-To: <CAHYQbfAG5878M0x0jJPB4sD-Ut1dh_Jeuqop7P=r=ZFyL0iBwA@mail.gmail.com>

On Wed, 2014-12-31 at 01:16 -0500, Jacob Ritorto wrote:
> Hey, thanks, Derrik.
>   I don't mess with Linux much (kind of an Illumos junkie by trade ;),
> but I bet gcc would.  I did out of curiosity do it with the Macintosh
> cc (Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn))
> and it throws warnings about our not type-defining functions because
> you're apparently supposed to do this explicitly these days, but it
> dutifully goes on to assume int and compiles our test K&R stuff mostly
> fine.  It does unfortunately balk pretty badly at the naked returns we
> initially had, though.  Wish it didn't because it strikes me as being
> beautifully simple..
> 
It compiles and runs with no warnings or any issues with gcc 4.9.2 on
Fedora 21.

Like so many x-gener Linux guys, I was a UNIX guy in the early '90's,
and just fell into Linux.  

So, you are running BSD 2.11, on a real PDP-11 ( or is it a VAX ),  in
your house? Or are you using an emulator? Either way, that's still
probably no small feat.

I have a Mac Plus emulator ( MiniVMac ) that I installed MachTen on,
just to see if I could get it running, and it works.

( MachTen is this odd sort of UNIX that was available for the Mac in the
'90's, that runs on top of Mac OS ).
> 
> thx again for the encouragement!
> jake
> 
No problem.  Anyone getting the younger ones into the older technology
is good! 

- Derrik 





  reply	other threads:[~2014-12-31  7:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 22:56 [TUHS] I swear! I rtfm'ed Jacob Ritorto
2014-12-30 22:59 ` Milo Velimirovic
2014-12-30 23:03 ` Larry McVoy
2014-12-31  0:03   ` Steve Nickolas
2014-12-30 23:05 ` Warren Toomey
2014-12-31  0:01   ` Jacob Ritorto
2014-12-31  2:22     ` Dan Stromberg
2014-12-31  2:33       ` Mary Ann Horton
2014-12-31  5:44         ` Jacob Ritorto
2014-12-31  6:02           ` [TUHS] K&R C on a modern Linux box? ( was Re: I swear! I rtfm'ed ) Derrik Walker v2.0
2014-12-31  6:16             ` Jacob Ritorto
2014-12-31  7:52               ` Derrik Walker v2.0 [this message]
2014-12-31  6:24   ` [TUHS] I swear! I rtfm'ed Dave Horsfall
2014-12-31  6:36     ` Lyndon Nerenberg
2014-12-31 14:58       ` Tim Bradshaw
2014-12-31 15:31         ` arnold
2014-12-31 15:37           ` Milo Velimirovic
2014-12-31 17:37             ` Derrik Walker v2.0
2014-12-31 20:09               ` Larry McVoy
2014-12-31 22:25                 ` Jacob Ritorto
2014-12-31 16:11       ` Mary Ann Horton
2014-12-31 20:14 ` Clem Cole
2014-12-31 20:45   ` Erik E. Fair
2014-12-31 21:05     ` Clem Cole
2014-12-31 22:30       ` Jacob Ritorto
2014-12-31 23:06         ` Mary Ann Horton
2014-12-31 23:11           ` Jacob Ritorto
2015-01-01 15:45         ` Clem Cole

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=1420012366.2068.13.camel@doomd.net \
    --to=dwalker@doomd.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).