Kevin Ryde <[EMAIL PROTECTED]> writes:
> Marius Vollmer <[EMAIL PROTECTED]> writes:
>>
>> We we already warn when importing something that shadows a core
>> definition, so we could as well warn when redefining one.
>
> I thought about that for my lint program and decided it'd be too
> annoying to
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>> I like this variant best. I don't think that writing strings with
>> lots of escape sequences to an unbuffered port happens often enough to
>> justify implementing a second buffering mechanism.
>>
>> When outputting an escaped char, we can additional
Neil Jerram <[EMAIL PROTECTED]> writes:
> 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?
Yes, and vice versa.
> By the way, has your idea about having "identifier -> m
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> There is probably code that relies on redefinitions being silently
> interpreted as a `set!', I'm afraid. So I don't think Guile should
> start issuing warnings for redefinitions by default.
The warnings would be about redefinitions that would not ha
Marius Vollmer <[EMAIL PROTECTED]> writes:
> I will make that change myself in the next days, but if anyone beats
> me to it...
Here is a patch for what I have in mind. I have applied it already.
Index: libguile/print.c
===
RCS fil
