Hello. When writing multi-module application I've found that Chicken searches for extensions in repository only and import libraries in the supplied include-path's additionally. Judging from the sources, this behaviour is intentional. Doesn't it make more sense to always search in user supplied include paths first, and the repository path last, similar to how C compilers search <> includes?
Current approach gives problems when I have previous versions of the modules already installed and try to compile a new with changed exports. Chicken seem to use the import libraries from the repository which gives "module unresolved" errors. This forces me to compile and install modules one-by-one which is quite fragile for larger applications (build failed for example, the repository is left with some old and some new modules). There is setup-mode option but it is not scalable for multiple executables needing multiple modules. -- Regards, Oleg _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
