From: Noah Evans <noah.evans@cwru.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] multiple inputs
Date: Thu, 1 Apr 2004 12:34:42 -0500 [thread overview]
Message-ID: <4623606e74a91925b510cd480e7738da@cwru.edu> (raw)
In-Reply-To: <810c47b392ed21dbd01b75286fa1ec73@vitanuova.com>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
Right. But that's the point.
What hygenic macros are(to me) a way of creating domain specific languages based on C.
This can, when used badly, lead to unmaintainable software. You're exactly right.
At the same time as Russ said it can abstract a complex and opaque computation and clarify its intention.
To bring the subject of macros back to the subject of Plan 9, I made the initial comment thinking about a way to make the shell less dangerous when it expands metacharacters(in other words, protect me from myself). It's only an intuition, and I wanted to see what everyone thought of it.
Noah
[-- Attachment #2: Type: message/rfc822, Size: 2831 bytes --]
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] multiple inputs
Date: Thu, 01 Apr 2004 19:42:27 +0100
Message-ID: <810c47b392ed21dbd01b75286fa1ec73@vitanuova.com>
> I think the idea of the hygenic macro [...]
one way or another you're talking about syntax transformation, so the
syntax of the program you read is not that which is documented in the
language reference manual.
i think that this can easily lead to unmaintainable software. others
disagree.
off topic, anyway...
next prev parent reply other threads:[~2004-04-01 17:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 6:53 npe
2004-03-30 8:22 ` matt
2004-03-30 11:48 ` glenda
2004-03-30 14:03 ` matt
2004-03-30 12:10 ` glenda
2004-03-30 16:07 ` rog
2004-03-30 14:15 ` Noah Evans
2004-03-30 16:25 ` rog
2004-03-30 16:14 ` Noah Evans
2004-03-30 18:27 ` rog
2004-03-30 16:28 ` Noah Evans
2004-03-31 20:22 ` boyd, rounin
2004-04-01 13:01 ` Noah Evans
2004-04-01 15:31 ` rog
2004-04-01 14:43 ` boyd, rounin
2004-04-01 16:26 ` Russ Cox
2004-04-01 17:36 ` rog
2004-04-01 15:58 ` Noah Evans
2004-04-01 18:42 ` rog
2004-04-01 17:34 ` Noah Evans [this message]
2004-04-01 19:47 ` rog
2004-04-01 18:02 ` Noah Evans
2004-04-02 1:48 ` Geoff Collyer
2004-04-01 20:04 ` David Tolpin
2004-04-02 1:46 ` Geoff Collyer
2004-04-02 2:09 Noah Evans
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=4623606e74a91925b510cd480e7738da@cwru.edu \
--to=noah.evans@cwru.edu \
--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).