From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] too good to pass up
Date: Fri, 28 Apr 2006 09:00:00 -0400 [thread overview]
Message-ID: <f49ea572e0608b084e056d4a3b76a5a1@coraid.com> (raw)
In-Reply-To: <383a34aca230dbcd89d76b9929cfc8c5@collyer.net>
> Not that I'm defending writing C as
> though it were Algol 68...
I kind of liked it after the initial shock.
Even inspired the Obfuscated C Contest.
I don't think SRB's code was obfuscated, though.
next prev parent reply other threads:[~2006-04-28 13:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 22:45 Ronald G Minnich
2006-04-27 22:57 ` Roman Shaposhnick
2006-04-27 22:58 ` Brantley Coile
2006-04-28 0:45 ` Roman Shaposhnick
2006-04-28 1:02 ` geoff
2006-04-28 13:00 ` Brantley Coile [this message]
2006-05-02 14:41 ` Aharon Robbins
2006-05-03 1:49 ` geoff
2006-04-27 23:58 ` geoff
2006-04-28 6:39 ` David Leimbach
2006-04-28 6:59 ` David Leimbach
2006-04-28 7:01 ` David Leimbach
2006-04-28 0:01 erik quanstrom
2006-04-28 13:01 erik quanstrom
2006-04-28 21:57 ` Charles Forsyth
2006-05-02 3:29 Ronald G Minnich
2006-05-02 5:10 ` Noah Evans
2006-05-02 6:11 ` Martin C. Atkins
2006-05-02 23:30 ` David Leimbach
2006-05-02 23:46 ` Skip Tavakkolian
2006-05-02 23:53 dmr
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=f49ea572e0608b084e056d4a3b76a5a1@coraid.com \
--to=brantley@coraid.com \
--cc=9fans@cse.psu.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).