[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] set! on unbound variable

From: Jinsong Liang
Subject: Re: [Chicken-users] set! on unbound variable
Date: Fri, 23 Sep 2016 23:25:49 -0400

Then I think this seriously deserves a warning, because the code is not only against the standard, but potentially a bug, as shown in my case.

Thank you everyone for your help!



On Fri, Sep 23, 2016 at 9:47 PM, Evan Hanson <address@hidden> wrote:
Hi Jinsong,

Not a bug, but certainly something that can be confusing if you don't
expect it. In your example, `helo` is implicitly defined as a toplevel
variable at the point of `set!.

The difference is noted (very, very succinctly) in the manual here:

Unfortunately there's not currently a way to generate a warning in this
situation, that I know of.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]