Re: Module name == dir hierarchy seems to make devel awkward...

[Rob Browning]

Martin Grabmueller <address@hidden> writes:

> A more complicated solution would be to define additional name
> mapping rules, maybe in a configuration file.  Personally, I dislike
> this, because it complicates implementation, usage and maintainance
> without helping much.

Right, I believe this is how slib does things, but as you mention,
it's got it's own set of problems.

I just wanted to bring up the issue to make sure we'd considered it.
If there's no easy workaround, and we just need to live with the
inconvenience, then that's fine too.

Wait a minute.  I just thought of something that might work fairly
well if it's not considered too kludgy.  I wonder if we could add
something like a module mapping registry to guile.  It would normally
be empty, and so in the standard case, modules would just work the way
they always have, where you search %load-path until you find the right
file in the right relative place, but we'd also have a mechanism by
which you can say:

  (set-module-to-path-mapping! '(foo bar baz) "./baz.scm")

and this setting would be consulted first, before trying the normal
search mechanism.  In the general case, you'd never use this mapping,
but when you're developing, you could use it to avoid the deep empty
hierarchies.

Not sure it's a great idea, but it's an idea :>

-- 
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930