From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] C is me
Date: Wed, 30 May 2007 20:53:23 +1000 [thread overview]
Message-ID: <775b8d190705300353h1efe8a1cu33f5e0eb9e5dc854@mail.gmail.com> (raw)
In-Reply-To: <2rydncTa6Pj4bsHbnZ2dnUVZ_qyjnZ2d@comcast.com>
what else should i learn, except to be surprised by them screwing with me?
do tell.
brucee
On 5/30/07, Douglas A. Gwyn <DAGwyn@null.net> wrote:
> "Bruce Ellis" <bruce.ellis@gmail.com> wrote...
> > ok. well i declared a string today "/??/n:", because that's
> > what iomangler throws at me as a prefix, at times.
>
> Perhaps if you'd learned about trigraphs instead of griping about them,
> you'd at least have suspected there could be a problem. At least there
> is a simple workaround.
>
> P.S. I think it was a mistake for the standard not to also provide a
> trigraph sequence that expands to ?. It would make automated
> code generation easier.
>
prev parent reply other threads:[~2007-05-30 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 7:43 Bruce Ellis
2007-05-29 15:18 ` tlaronde
2007-05-30 8:31 ` Douglas A. Gwyn
2007-05-30 10:53 ` Bruce Ellis [this message]
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=775b8d190705300353h1efe8a1cu33f5e0eb9e5dc854@mail.gmail.com \
--to=bruce.ellis@gmail.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).