From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: New syntax: (: MODULE-NAME VARIABLE-NAME)
Date: 16 Nov 2003 18:38:24 +0000 [thread overview]
Message-ID: <m3r808w44f.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <m3y8ugw4ye.fsf@laruns.ossau.uklinux.net>
>>>>> "Marius" == Marius Vollmer <mvo@zagadka.de> writes:
Marius> Hmm, I would find it more natural to have a separate macro, like
Marius> (:: MOD-NAME VAR-NAME)
Marius> where '::' would be the (to me) obvious choice of name.
Marius> Unfortunately, with (read-set! keyword 'prefix) that name would be a
Marius> keyword...
Sorry that my thoughts on this are coming out in such a trickle!
I just noticed, though, that there are some other symbols (than :)
available that don't have other meanings and which could be understood
as relevant to a module lookup:
(@ MOD-NAME VAR-NAME)
Seems quite good, with @ meaning `at' as in `in the specified module'.
($ MOD-NAME VAR-NAME)
Tenuous link to $'s use in many languages for variable reference.
Clashes with not-yet-widespread use of $ for value-history, though.
(. MOD-NAME VAR-NAME)
Intuitively very similar to : IMO, but without the keyword issues.
However, (i) some people might want `.' for the mathematical dot
(scalar) product; (ii) Guile currently seems confused about whether
`.' is a symbol:
guile> .
ERROR: Unbound variable: .
ABORT: (unbound-variable)
guile> '.
.
guile> (define . 1)
ERROR: In procedure memoization:
ERROR: In line 3: Bad expression (define . 1).
ABORT: (syntax-error)
(? MOD-NAME VAR-NAME)
Quite nice, ? meaning a query, so a lookup.
Of these, I like @ the most.
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-11-16 18:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 18:12 New syntax: (: MODULE-NAME VARIABLE-NAME) Marius Vollmer
2003-11-13 19:47 ` Neil Jerram
2003-11-13 20:58 ` Marius Vollmer
2003-11-14 21:04 ` Neil Jerram
2003-11-15 15:19 ` Marius Vollmer
2003-11-15 19:22 ` Neil Jerram
2003-11-16 17:31 ` Marius Vollmer
2003-11-16 18:20 ` Neil Jerram
2003-11-16 18:38 ` Neil Jerram [this message]
2003-11-16 20:36 ` Marius Vollmer
2003-11-17 20:18 ` Neil Jerram
2003-11-17 21:34 ` Marius Vollmer
2003-11-16 20:28 ` Marius Vollmer
2003-11-14 22:09 ` Mikael Djurfeldt
2003-11-15 15:10 ` Marius Vollmer
2003-11-17 2:00 ` Mikael Djurfeldt
2003-11-17 14:41 ` Marius Vollmer
2003-11-16 8:02 ` Dirk Herrmann
2003-11-17 14:44 ` New syntax (@ MODULE-NAME VARIABLE-NAME) committed Marius Vollmer
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r808w44f.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).