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?
Afficher les réponses par date
but with Blackhole's import there is not any indication of error until runtime.
The same happens in the plain Gambit *interpreter*, so it may just be a fact on whether you compile or not.
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?
The gambit-modules-list was originally created on my initiative to serve the development of underpinnings to be used by the various module systems to make them interoperate well. But I've then never pursued the effort, first because of time constraints, then because I've changed direction of my work. So the list has only be used for discussion of Blackhole. It's up to users or Per to decide whether discussion on Blackhole should be concentrated there or on the main Gambit mailing list.
Christian.
Really slow reply.. I have now fixed this, so that warning messages are emitted when importing compiled modules.
/Per
11 feb 2010 kl. 14.35 skrev Tomi Neste:
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 _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
-
Christian Jaeger -
Per Eckerdal -
Tomi Neste