From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] A probably stupid question on portability
Date: Wed, 24 Oct 2007 08:58:38 +0000 [thread overview]
Message-ID: <471E5BE6.F79F7A3D@null.net> (raw)
In-Reply-To: <e549296ffa1c11d7aee1113a2c431228@terzarima.net>
Charles Forsyth wrote:
> the rot really set in with reiser
> This new version [of the preprocessor] was written by John F. Reiser and is from 5 to 12
> times faster than the old.
> (but the input language was considerably more elaborate, and didn't people use it!)
Virtually all the Reiser cpp features were used by a lot of code.
Some code even exploited differences between what K&R1 Appendix A
said and what the Reiser cpp actually did, such as substitution
within string literals.
next prev parent reply other threads:[~2007-10-24 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 19:10 ron minnich
2007-10-23 19:14 ` Pietro Gagliardi
2007-10-23 20:03 ` Charles Forsyth
2007-10-23 20:12 ` Pietro Gagliardi
2007-10-24 8:58 ` Douglas A. Gwyn [this message]
2007-10-24 9:21 ` Charles Forsyth
2007-10-23 22:27 ` David Leimbach
2007-10-23 22:41 ` Pietro Gagliardi
2007-10-24 8:58 ` Douglas A. Gwyn
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=471E5BE6.F79F7A3D@null.net \
--to=dagwyn@null.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).