Re: [Chicken-users] loading libraries: inconsistencies interpreter vs. compiler
On 6/13/05, felix winkelmann <[EMAIL PROTECTED]> wrote: > On 6/12/05, Michele Simionato <[EMAIL PROTECTED]> wrote: > Moreover specifying directories with require-extension is not > allowed (...and will be documented right now. ;-) Ok, but then it should NOT work in the interpreter! It gives false hopes and expectations ... Michele ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] loading libraries: inconsistencies interpreter vs. compiler
On 6/13/05, Michele Simionato <[EMAIL PROTECTED]> wrote: > > But then, how am I supposed to write a package (package=directory > containing various modules and possibily subpackages)? > The "extension" namespace is flat. You would need a common package prefix for that. Or you implement an extension specifier that maps to a separate directory: (use my-package) ; registers an ext-spec at compile-time (use (my-package lib ...)) cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] loading libraries: inconsistencies interpreter vs. compiler
On 6/13/05, felix winkelmann <[EMAIL PROTECTED]> wrote: > On 6/12/05, Michele Simionato <[EMAIL PROTECTED]> wrote: > > I have a library in a subdirectory of CHICKEN_INCLUDE_PATH, say in > > mystuff/mylib. In the interpreter, from any directory I do > > > > (require-extension mystuff/mylib) > > > > CHICKEN_INCLUDE_PATH is not intended to be used for > libraries (eggs), but for include-files (loaded via `include'). > Moreover specifying directories with require-extension is not > allowed (...and will be documented right now. ;-) > But then, how am I supposed to write a package (package=directory containing various modules and possibily subpackages)? Michele Simionato ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] loading libraries: inconsistencies interpreter vs. compiler
On 6/12/05, Michele Simionato <[EMAIL PROTECTED]> wrote: > I have a library in a subdirectory of CHICKEN_INCLUDE_PATH, say in > mystuff/mylib. In the interpreter, from any directory I do > > (require-extension mystuff/mylib) > CHICKEN_INCLUDE_PATH is not intended to be used for libraries (eggs), but for include-files (loaded via `include'). Moreover specifying directories with require-extension is not allowed (...and will be documented right now. ;-) cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
