From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: case syntax and symbols
Date: Mon, 23 May 2005 19:39:42 +0100 [thread overview]
Message-ID: <4292236E.1050000@ossau.uklinux.net> (raw)
In-Reply-To: <874qcv40q4.fsf@zagadka.de>
Marius Vollmer wrote:
>
> Hmm. There are two things here that might want a warning: redefining
> something that was a macro as a variable;
Sounds good; and vice versa? By the way, has your idea about having
"identifier -> macro" instead of "identifier -> variable -> macro" been
implemented yet?
> and shadowing a core definition.
I'm not sure I like the implication of "core", as it suggests different
behaviour for privileged Guile code, vs. different layers of user code.
Isn't the rule we want "whenever a new definition shadows an existing
definition in a module, and the existing definition did not originate in
the current module"? This rule would also avoid giving unwanted
warnings when an edited module is reloaded.
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-05-23 18:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 22:57 case syntax and symbols Aaron VanDevender
2005-03-22 0:53 ` Marius Vollmer
2005-03-22 7:21 ` Neil Jerram
2005-05-22 17:41 ` Marius Vollmer
2005-05-23 1:58 ` Kevin Ryde
2005-06-06 19:21 ` Marius Vollmer
2005-05-23 18:39 ` Neil Jerram [this message]
2005-05-24 11:39 ` Ludovic Courtès
2005-05-24 18:01 ` Neil Jerram
2005-05-26 10:53 ` Ludovic Courtès
2005-05-26 18:30 ` Neil Jerram
2005-06-06 19:26 ` Marius Vollmer
2005-06-06 19:23 ` Marius Vollmer
2005-03-22 9:17 ` Ludovic Courtès
2005-03-22 13:23 ` Marius Vollmer
2005-03-22 15:28 ` Ludovic Courtès
2005-03-22 16:28 ` 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=4292236E.1050000@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@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).