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

[Jinsong Liang]

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!

Jinsong

 

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:

  http://wiki.call-cc.org/man/4/Extensions%20to%20the%20standard#set

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

Cheers,

Evan