This is the mail archive of the
guile@cygnus.com
mailing list for the Guile project.
Re: Where should guile modules store meta data?
Jost Boekemeier <jostobfe@calvados.zrz.TU-Berlin.DE> writes:
> > Also, with a two file system it seems like you will force a tight
> > binding between files and modules.
>
> Yes. This is neccesary.
>
>
> > Why aren't modules and files orthogonal concepts.
>
> A module *is* a file with an interface. It seems to me that when you
> are talking about modules, you really mean a different concept: name
> spaces or "environments".
Actually this touches another point. It would be *highly* convenient
not to be forced to worry about two files at the same time (interface
and implementation). So I think that such module system will need some
sort of automated interface generation. In that case, it really
doesn't matter if a set of file produces a single interface or a
single file compiles into multiple interfaces.
OTOH, I still don't see the necessity for the interface files. What
would happen in the application after loading the interface?
(remember, Guile doesn't have declarations).
--
I refuse to use .sig