From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: plan 9 newbie...!!!!!
Date: Thu, 20 Dec 2007 15:57:13 +0000 [thread overview]
Message-ID: <122020071557.24261.476A90D900029B1A00005EC522193100029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> (raw)
> just escaped AOL. If you actually do some coding, r
> emember that it's "if (!foo)", not "if.......(!!!!!!!!foo)".
Yeah, but if you've got an odd number of bangs
(add one to what you've put), it'll give the
same result.:-) Great for the obfuscated C
contest.
(Ducks for cover...)
BLS
next reply other threads:[~2007-12-20 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 15:57 Brian L. Stuart [this message]
2007-12-20 16:39 ` john
-- strict thread matches above, loose matches on Subject: below --
2007-12-20 17:05 Brian L. Stuart
2007-12-20 14:57 James.Deagle
2007-12-20 10:39 [9fans] " codewarrior85
2007-12-20 14:00 ` [9fans] " codewarrior85
2007-12-20 15:53 ` john
2007-12-20 16:52 ` codewarrior85
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=122020071557.24261.476A90D900029B1A00005EC522193100029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net \
--to=blstuart@bellsouth.net \
--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).