This is the mail archive of the guile@cygnus.com mailing list for the guile project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
>Whether this is a bug or not can be discussed. Guile has its own >module system which should be used for Guile programs. > >The purpose of the Guile slib interface (ice-9 slib) is only to make >slib packages available to the user. > >`library-vicinity' is defined within the (ice-9 slib) module so that >the slib code can see it, but it isn't exported. This is the kind of detail regarding modules I can't seem to find in the guile manual. There is obviously a lot about modules I don't yet fathom. Why should it be visible? Three reasons I can think of.... (1) The SLIB manual says that it should be visible. (2) Since SLIB doesn't know about guile modules, I imagine everything else in SLIB is visible too, so why should it be different? (3) There is code out there that uses it. On a more practical note, the reason I want it visible is that xscm uses it. Exactly why it does isn't immediately obvious because I'm still struggling with the SLIB packaging system as well. >Currently, I can't see any reason why it should be exported, except >possibly for the case when you are developing a new slib library in >Guile. > >Why do you want to access `library-vicinity'?