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] |
Jim Blandy <jimb@red-bean.com> writes: > (Hoping to resurrect a promising topic...) A definite success. [ snip ] > Names by logical category > The name reflects the features provided or the job done by the > module. Examples: > (posix ...) POSIX stuff > (shell ...) Exec'ing Unix commands, parsing arguments, etc. > (net ...) networking > (gui ...) GUI toolkit interfaces, and related things > (math ...) Mathematical functions > > (guile ...) > Modules that come with the Guile core, and don't fall nicely into > one of the categories above, or give access to some part of the > Guile interpreter (and whose logical category is therefore > "guile"!). Low-level interfaces that are tamed by some other > module would go here too: > > (guile debug) interface between a debugger written > in Scheme, and Guile's interpreter > (guile internal load) all the weird load variants, that > get redefined by the module system > > (app APPNAME ...) > Modules that come with an application and only make sense in the > context of that application. For example, SCWM might provide its > functions here. > > (chaos ...) > Safety valve, like Usenet's `alt'. Guile and the Guile modules > group will never complain about anything anyone puts here. I'd add: (RFI ...) The submodules have the names (numbers?) of cataloged RFI's. For instance, Olin Shivers' list lib will probably be (I'm making it up) RFI #1, and any program that relies on it would be able to say: (use-modules (rfi 1)) ;use the common list functions. [ snip ] mike.