Re:
> If I understand your description correctly, the problem is
> passing both named and unnamed arguments to callNextMethod().
No, as I said the distinction is a potential bug in callNextMethod
_whenever_ it gets explicit arguments. (At the moment, it seems to be a
bug in substitute() or el
On Fri, 5 Aug 2005, John Chambers wrote:
> Paul Roebuck wrote:
>
> > Can someone explain what the problem is when I use the
> > generating function? And how to get debug() to stop in
> > the Superclass initialize method?
> > [SNIP code & output]
>
> Now, the specific example. There are 3 special
First, anyone planning to debug methods should consider the general form
of the trace() function with signature= to say what method to trace, and
some suitable interactive function such as "browser" or "recover" to
examine the computations. See ?trace
In this example, something like:
trace("
