The bug should now be fixed. The actual change is very small, but it
enforces a semantic definition that may be relevant, so we should
discuss it.
The question is: what method does callNextMethod() refer to? The
definition now enforced is: the "next method" is the method found for
the defi
John Chambers <[EMAIL PROTECTED]> writes:
> It's a bug resulting from the combination of:
> 1. multiple recursive levels of callNextMethod()
> 2. nonstandard arguments in the method definition; that is, (.Object,
> x) vs .Object, ...) for the generic.
Thanks for the explanation and work aro
It's a bug resulting from the combination of:
1. multiple recursive levels of callNextMethod()
2. nonstandard arguments in the method definition; that is, (.Object,
x) vs .Object, ...) for the generic.
Specifically, the callNextMethod code tries to build up a list of
"excluded" classes, but in
Hi,
Given a simple three class hierarchy: A <-- B <-- C
I want to define an initialize method for each class such that when I
call new("C", x=5), the initialize methods for A and B are used to
incrementally build the object.
When I do what seems obvious to me using callNextMethod, I get an
infin
