From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Oldest Unix source code still in modern systems
Date: Tue, 22 May 2012 17:35:10 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.00.1205221710170.83604@aneurin.horsfall.org> (raw)
In-Reply-To: <1337616921.5781.YahooMailClassic@web184718.mail.ne1.yahoo.com>
On Mon, 21 May 2012, Michael Davidson wrote:
> /*
> * you are not expected to understand this.
> */
Line 2238, of course :-) For any youngsters here, that code is *subtle*.
Vale, both DMR and Dr John Lions (my lecturer at UNSW).
> That would certainly still be appropriate for the Linux context switch
> code which, last time I looked, was a horrible mess of gcc "asm"
> constructs glued together with C preprocessor macros.
Typical Penguin/OS. I am in stitches.
> The comment that I miss most, however, is:
>
> /*
> * printf should not be used for chit chat
> */
My favourite too :-) We ended up implementing the call via the TTY
interface, so that our 11/40 would not be brought to her knees.
-- Dave
next prev parent reply other threads:[~2012-05-22 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 5:18 Warren Toomey
2012-05-21 15:00 ` Jeremy C. Reed
2012-05-21 15:43 ` Armando Stettner
2012-05-21 16:15 ` Michael Davidson
2012-05-22 7:35 ` Dave Horsfall [this message]
2012-05-21 7:45 arnold
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=alpine.BSF.2.00.1205221710170.83604@aneurin.horsfall.org \
--to=dave@horsfall.org \
/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).