Hi Matt,

A simple solution might be to keep your implementation in one file and
your module form in another that includes it. Then, your tests could
`include` or `load-relative` or whatever the implementation file rather
than the module, making all its definitions visible.

This may not work for your situation, but it's straightforward if you'll
always be testing with the source present.

Cheers,

Evan

_______________________________________________
Chicken-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-users

Reply via email to