This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: closures for GOOPS privates
Klaus Schilling <Klaus.Schilling@munich.netsurf.de> writes:
> Jost Boekemeier writes:
> > >
> > That's why I will implement two solutions by the end of next month: a)
> > The module /has/ one or more classes (which seems to be the preferred
> > solution at the moment and is also easy to implement) and b) the
> > module /is a/ class (my preferred solution and also the right thing
> > (TM) to do :>).
>
> Will this new system also support reloading of modules on demand
> (e.g. if the file containing the module's code changed ), importing
> of only specified identifiers and renaming of imported identifiers?
It would also be a good idea to pass this design by the list, just to
make sure that you're not siccing your own (talking to Jost, here)
design on the audience that has rather disparate idea of what
constitutes the Right Thing.
It may be just my personal bias, but from the discussion on the list I
got an impression that you seem to be operating in a programming
paradigm rather disconnected from Scheme/CLOS world. I don't think
it'd be nice to other Guile developers to create a module system that
does something Eiffelish or C++ish that is at odds to LISP/Scheme way
of doing things.
--
How to eff the ineffable?