Brent Pinkney writes:
> How does that work in an environment where you are using third party
> libraries, lice srfi, ice-9, guile-lib, etc as well as your own code.
Okay, I have a guess about what you meant here. Suppose two
independently developed modules add methods to generics with the same
n
Mark H Weaver wrote:
> The proper solution is as follows:
>
> * Every generic function must be defined (using 'define-generic') and
> exported from one (and only one) module.
>
> * Every module that uses a generic function, or adds a method to it (and
> that includes slot accessors), must firs
On 15/03/2013 02:11, dsm...@roadrunner.com wrote:
Mark H Weaver wrote:
The proper solution is as follows:
* Every generic function must be defined (using 'define-generic') and
exported from one (and only one) module.
* Every module that uses a generic function, or adds a method to it
Mark H Weaver wrote:
> The proper solution is as follows:
>
> * Every generic function must be defined (using 'define-generic') and
> exported from one (and only one) module.
>
> * Every module that uses a generic function, or adds a method to it (and
> that includes slot accessors), m
Hi Brent,
Brent Pinkney writes:
> I am having serious problems exporting generics from subclasses of
> and then using them in other modules.
Apologies for the confusion. You're not the only one who's been having
trouble with this. There *is* a proper solution, which I will describe
below, but
Hello Brent,
Please send the code, i'll look at it asap.
I am precisely in a discussion with developers about goops and the way the guile
module system interferes with it, since i also believe that there is a serious
problem indeed: and not 'just' because there is no way to ask goops 'stuff' to
