I just wanted to comment on the naming.
Thanks. This sounds like good advice.
Out of interest, I recently released HaXml as a hierarchical library "package" for ghc and nhc98. Obviously I'd like it to work with Hugs as well. What would be the "official" way for a third-party package like mine to integrate itself into a pre-existing Hugs installation?
I don't know about 'official' but the way I'd do it is: - unpack the module somewhere ($prefix/lib/hugs/lib/$pkgname would be a fine choice but other places are good too) - run hugs +G on any ffiable libraries - add -P$prefix/lib/hugs/lib/$pkgname: (or whatever) to HUGSFLAGS Obviously, the last step isn't very convenient to script. There's various ways this could be fixed (wrapper scripts which generate search paths from a list of installed packages and then invoke Hugs, adding package support directly to Hugs, using the search path as a list of directories that might contain _packages_ (instead of as a list of directories that might contain _modules_)) but I don't think Hugs has any at the moment. -- Alastair