|Subject:||Re: [Chicken-users] set! on unbound variable|
|Date:||Fri, 23 Sep 2016 23:25:49 -0400|
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.
|[Prev in Thread]||Current Thread||[Next in Thread]|