Oleg Kolosov scripsit: > 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?
I agree that that would be better. What was the reason for searching the repository first? -- John Cowan http://www.ccil.org/~cowan [email protected] Even a refrigerator can conform to the XML Infoset, as long as it has a door sticker saying "No information items inside". --Eve Maler _______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
