I have a situation that resembles the following, where I have a
definition |foo| that calls an undefined-by-the-module |bar|:
<++> t.setup
(compile -s t.scm)
(install-extension 't `("t.so" "t.import.so"))
<-->
<++> t.scm
(module t
*
(import scheme)
(import chicken)
(define (foo)
(bar)))
<-->
Running chicken-install, I get the following warning and error:
Warning: reference to possibly unbound identifier `bar' in:
Warning: foo
Error: module unresolved: t
Reading the code, it seems the above warning is converted to a
fatal error, though there may be cases where it does not.
Here is my problem:
I have an egg that, while initializing, defines bar, but bar isn't
defined at compile-time, so I'm getting this error. This works
when I compile the code outside of a module, but there seems to be
an additional constraint when I wrap it around (module ...).
Can I tell chicken-install that I know this symbol is undefined,
and that things will be ok? Do I need to create a compile-time
dummy definition? How should I handle cases where my egg uses
but doesn't define a symbol in the runtime environment?
Thank you,
-a
--
my personal website: http://c0redump.org/
_______________________________________________
Chicken-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-users
