On Wed, Aug 28, 2002 at 11:13:59AM +0100, Alastair Reid wrote:
This reminds me: what are we going to use as the default path?
We could use the old path (lib, lib/exts, lib/hugs) but then people don't see the new stuff.
We could use the new path (libraries, oldlibs) but then runhugs doesn't work (it needs HugsDynamic).
We could use both (libraries, oldlibs, lib, lib/exts, lib/hugs) but then a number of things report having duplicate instances for Int. (I think this comes from the Int module itself).
Yes, using both won't work (duplicate instances, ambiguous references). I use -P{Hugs}/libraries:{Hugs}/oldlib:{Hugs}/lib/hugs and that seems to provide both old and new interfaces. (In your example, lib/hugs/HugsDynamic brings in oldlib/IOExts, which is a wrapper around libraries stuff.) However I don't think this has had wide enough use to trust as the default in this release, so I'd suggest leaving the default path unchanged and mentioning this alternative in the documentation (but having both installed, so they can choose at run-time).