[gambit-list] Blackhole and undefined variables.

Tomi Neste tomi.neste at gmail.com
Thu Feb 11 08:35:10 EST 2010


It seems that Blackhole doesn't give any warnings when importing modules
with undefined identifiers. With vanilla Gambit when loading files with
undefined variables I get the '*** WARNING -- Variable "bar" used in module
"foo.o1" is undefined' message but with Blackhole's import there is not any
indication of error until runtime.

Could Blackhole be modified to give a warning (or even an error?) when this
happens. If I have understood correctly, situation where an identifier is
not defined in the current or any of the imported modules is always on error
anyway (except for the identifiers defined in the Gambits standard
library...)?

It would be an nice feature to have since tracking the undefined variables
(especially in compiled code which only gives the rather obscure runtime
error 'Operator is not a PROCEDURE (#!unbound ...)' message) can be quite
annoying some times.

PS. What is the policy on Blackhole related discussion? I see that there is
also an (very quiet) mailing list for it, should that be used instead?

-- 
tomppa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.iro.umontreal.ca/pipermail/gambit-list/attachments/20100211/bcba2bca/attachment.htm>


More information about the Gambit-list mailing list