[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Scheme-reports] Replacing two identifiers with the same in an import declaration
- To: Marc Nieper-Wißkirchen <marc.nieper@x>
- Subject: Re: [Scheme-reports] Replacing two identifiers with the same in an import declaration
- From: John Cowan <cowan@x>
- Date: Sat, 25 Jan 2014 19:19:38 -0500
- Cc: scheme-reports <scheme-reports@x>
- In-reply-to: <CAEYrNrSS=e9RPwRqXJ-Qcv2AanE+YMaW8ZU4YMWB8awFjtzb1g@mail.gmail.com>
- References: <CAEYrNrR8HVNAn9eFjwLowM-XNT0ekqvGm-S0Ks0m2t7YX3tf8Q@mail.gmail.com> <CAEYrNrSS=e9RPwRqXJ-Qcv2AanE+YMaW8ZU4YMWB8awFjtzb1g@mail.gmail.com>
Marc Nieper-Wißkirchen scripsit:
> "In a program or library declaration, it is an error to import
> the same identifier more than once with different bindings,
> supposed to exclude the case (replace <import set> (foo bar) (foo baz))?
I think it does, though it was not intended to do so. The original purpose
was of course to prevent you from trying to import the same identifier
from different libraries.
> And (replace <import set> (foo bar) (baz bar)) is supposed to introduce two
> identifiers with the same binding?
I see no reason why not, though no reason for a user to do that, either.
The man that wanders far cowan@x
from the walking tree http://www.ccil.org/~cowan
--first line of a non-existent poem by: John Cowan
Scheme-reports mailing list