From: tfb@tfeb.org (tfb@tfeb.org)
Subject: [TUHS] Mac OS X is Unix
Date: Wed, 4 Jan 2017 17:14:33 +0000 [thread overview]
Message-ID: <2CB47146-0555-46C9-8A2A-F028EC1DE263@tfeb.org> (raw)
In-Reply-To: <CAEoi9W75CWcHvpOf9y9KJo7soFYVZtDwwhJnv5Ja_vejCfPJkw@mail.gmail.com>
On 4 Jan 2017, at 15:02, Dan Cross <crossd at gmail.com> wrote:
>
> What I'm proposing is almost exactly like Common Lisp's `#-` and `#+` (these use reader suppression, of course). Delving further into the realm of reader macros and other Lisp-like reader things is, I think, a mistake: the complexity of the reader is arguably a wart on the side of Common Lisp.
I kind of disagree about the CL reader in the context of CL, but strongly agree that such a thing would be a mistake for a C-family language. but yes, #+ & #- are what I'd like for a C-family language.
As you say statement languages make this a bit harder: I've never understood why anyone thought they were a good idea (I think a C-level expression-language ought to be reasonably easy to do).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170104/fa7967af/attachment.html>
prev parent reply other threads:[~2017-01-04 17:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 20:19 Doug McIlroy
2017-01-03 21:05 ` Charles Anthony
2017-01-03 21:33 ` [TUHS] When was #if introduced in C? (was: Re: Mac OS X is Unix) Michael Kjörling
2017-01-03 21:53 ` Robert Swierczek
2017-01-03 21:57 ` Clem Cole
2017-01-03 21:56 ` Clem Cole
2017-01-03 21:35 ` [TUHS] Mac OS X is Unix Clem Cole
2017-01-03 22:10 ` Lyndon Nerenberg
2017-01-03 21:39 ` Lyndon Nerenberg
2017-01-03 22:12 ` ron minnich
2017-01-03 23:39 ` Tim Bradshaw
2017-01-04 0:12 ` ron minnich
2017-01-04 9:11 ` Tim Bradshaw
2017-01-04 10:04 ` Álvaro Jurado
2017-01-04 0:13 ` Steve Johnson
2017-01-04 3:50 ` Dan Cross
2017-01-04 12:26 ` Tim Bradshaw
2017-01-04 13:49 ` Random832
2017-01-04 15:02 ` Dan Cross
2017-01-04 17:14 ` tfb [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=2CB47146-0555-46C9-8A2A-F028EC1DE263@tfeb.org \
--to=tfb@tfeb.org \
/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).