From: cdl@mpl.ucsd.edu (Carl Lowenstein)
Subject: [TUHS] So now that the source is finally out...
Date: Fri, 25 Jan 2002 11:18:31 -0800 (PST) [thread overview]
Message-ID: <200201251918.LAA23410@chiton.ucsd.edu> (raw)
> From: "P.A.Osborne" <P.A.Osborne at ukc.ac.uk>
> To: "M. Warner Losh" <imp at village.org>
> Cc: tuhs at minnie.tuhs.org
> Subject: Re: [TUHS] So now that the source is finally out...
> Date: Fri, 25 Jan 2002 11:16:37 +0000
>
> On Fri, Jan 25, 2002 at 03:27:25AM -0700, M. Warner Losh wrote:
> > Real as in 286 or as in 8088 :-).
>
>
> > gcc can compile K&R, but the language has evolved some since the v7
> > days. =*, =+, etc became *=, +=, etc. There are some other subtle
> > things too that I don't recall off the top of my head, but which vexed
> > the comp.lang.c news groups in the early 1980's.
>
> That makes things a challenge. Still the source of the kernel is
> around 10K lines IIRC and going through it in stages doesnt make life
> too painfull.
Doesn't one of the C beautifiers do that for you (rewrite =+ etc.)
Either GNU indent or Berkeley? cb.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenstein at ucsd.edu
next reply other threads:[~2002-01-25 19:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 19:18 Carl Lowenstein [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-31 1:03 John Holden
2002-01-30 1:40 Ken Wellsch
2002-01-27 19:03 norman
2002-01-26 14:50 Ken Wellsch
2002-01-27 23:58 ` Greg Lehey
2002-01-31 0:29 ` Joerg Micheel
2002-01-24 18:39 Rob Becker
2002-01-25 9:42 ` P.A.Osborne
2002-01-25 10:27 ` M. Warner Losh
2002-01-25 11:16 ` P.A.Osborne
2002-01-25 15:19 ` Ephrem Hugh Bensusan
2002-01-25 15:52 ` M. Warner Losh
2002-01-25 21:08 ` David C. Jenner
2002-01-25 16:24 ` Wolfgang Rupp
2002-01-29 6:17 ` M. Warner Losh
2002-01-25 16:30 ` Wolfgang Rupp
2002-01-25 17:30 ` Jeffrey S. Sharp
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=200201251918.LAA23410@chiton.ucsd.edu \
--to=cdl@mpl.ucsd.edu \
/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).