From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] APE inconsistencies
Date: Fri, 29 Mar 2013 22:37:59 -0400 [thread overview]
Message-ID: <299894e4d6e9869eeb1b646ac9dd22bb@9srv.net> (raw)
In-Reply-To: <20130329190345.GA2335@polynum.com>
> It should be indeed underlined that this is a compatibility
> feature, and not a POSIX feature.
APE does an excellent job of making that distinction clear.
Its use of defines to forcibly break syntax was quite
educational as a young programmer.
Anthony
next prev parent reply other threads:[~2013-03-30 2:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 17:13 Jeff Sickel
2013-03-29 17:20 ` Charles Forsyth
2013-03-29 17:25 ` Jeff Sickel
2013-03-29 17:41 ` Kurt H Maier
2013-03-29 18:00 ` Charles Forsyth
2013-03-29 18:26 ` Jeff Sickel
2013-03-29 19:03 ` tlaronde
2013-03-29 19:12 ` Kurt H Maier
2013-03-29 20:10 ` tlaronde
2013-03-29 20:32 ` Charles Forsyth
2013-03-30 2:37 ` a [this message]
2013-03-29 22:20 ` Lyndon Nerenberg
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=299894e4d6e9869eeb1b646ac9dd22bb@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/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).