From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: New syntax: (: MODULE-NAME VARIABLE-NAME)
Date: Sat, 15 Nov 2003 16:10:31 +0100 [thread overview]
Message-ID: <878ymhsm54.fsf@zagadka.ping.de> (raw)
In-Reply-To: <xy7smkqzjnt.fsf@chunk.mit.edu> (Mikael Djurfeldt's message of "Fri, 14 Nov 2003 17:09:58 -0500")
Mikael Djurfeldt <mdj@mit.edu> writes:
> Marius Vollmer <mvo@zagadka.de> writes:
>
>> what about making the changes below? The only unclean thing is that
>> we would need to change the interpretation of a single ':'.
>
> But isn't that pretty darn unclean? It changes the lexical structure
> of the language.
Hmm, yes and no. With the change, ':' remains a variable identifier
and the new syntax is actually a macro:
(define-macro (: mod-name var-name)
(let ((var (module-variable (resolve-interface mod-name) var-name)))
(if (not var)
(error "no such public variable" (list ': mod-name var-name)))
var))
That part is clean, I think, and doesn't change the lexical structure.
It only depends on an implementational detail and does something
officially that you can't do in Standard Scheme. However, Standard
Scheme doesn't have a module system either, and from that point of
view 'use-modules' etc already has changed the lexical structure
significantly.
> Note that we currently have an option which controls
> whether the reader conforms to R5RS ("Extended alphabetic characters
> may be used within identifiers as if they were letters.") or whether
> colon is marking a keyword, and that this option is defaulted to R5RS.
The reader is unchanged in the R5RS mode, only the non-R5RS mode now
treats an isolated colon differently:
;; R5RS
guile> (symbol? ':)
#t
guile> (keyword? '#:)
#t
;; non-R5RS with the change
guile> (read-set! keywords 'prefix)
guile> (symbol? ':)
#t
guile> (keyword? '#:)
#t
;; non-R5RS without the change
guile> (read-set! keywords 'prefix)
guile> (symbol? ':)
#f
guile> (keyword? ':)
#t
> I vote for using some syntax which is compatible with R5RS and would
> urge you strongly to at least keep the possibility to be compatible
> (=> new option controlling the interpretation of colon).
Given that the syntax is compatible, do you think we still need an
option for making (keyword ':) true again?
Here are the ChangeLog entries for the actual changes:
2003-10-24 Marius Vollmer <mvo@zagadka.de>
* read.c (scm_lreadr): Treat a single ':' always a symbol,
never as an empty keyword.
2003-10-23 Marius Vollmer <mvo@zagadka.de>
* eval.c (scm_m_generalized_set_x): Macroexpand the target when it
is a list. This allows (: ...) to work with set!.
* script.c (scm_compile_shell_switches): Use scm_c_read_string for
the "-e" option instead of scm_str2symbol. This allows things
like (: ...) to be specified for the entry point.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-11-15 15:10 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
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 [this message]
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=878ymhsm54.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--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).