unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-user@gnu.org
Subject: Re: case syntax and symbols
Date: Sun, 22 May 2005 20:41:39 +0300	[thread overview]
Message-ID: <874qcv40q4.fsf@zagadka.de> (raw)
In-Reply-To: <423FC796.4010303@ossau.uklinux.net> (Neil Jerram's message of "Tue, 22 Mar 2005 07:21:58 +0000")

Neil Jerram <neil@ossau.uklinux.net> writes:

>> Also (and don't try this at home kids):
>>   (define 'x (* x x))
>>   '2
>>   => 4
>
> And presumably (or in my view) this is all fine, except for the last
> example, where Guile should signal an error or at least give a
> warning. Right?

Hmm.  There are two things here that might want a warning: redefining
something that was a macro as a variable; and shadowing a core
definition.

We we already warn when importing something that shadows a core
definition, so we could as well warn when redefining one.

Opinions?

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2005-05-22 17:41 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 [this message]
2005-05-23  1:58       ` Kevin Ryde
2005-06-06 19:21         ` Marius Vollmer
2005-05-23 18:39       ` Neil Jerram
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=874qcv40q4.fsf@zagadka.de \
    --to=mvo@zagadka.de \
    --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).