Re: [Rd] methods cbind2 bind_activation disrupts cbind everywhere

2012-09-15 Thread Martin Morgan
On 09/14/2012 07:16 AM, Jeff Ryan wrote: Refreshing the memory on performance: http://r.789695.n4.nabble.com/reduce-limit-number-of-arguments-in-methods-cbind-td921600.html#a921601 short comment below... My issue had been resolved by a more careful approach taken by timeSeries. The other o

Re: [Rd] methods cbind2 bind_activation disrupts cbind everywhere

2012-09-14 Thread Jeff Ryan
Refreshing the memory on performance: http://r.789695.n4.nabble.com/reduce-limit-number-of-arguments-in-methods-cbind-td921600.html#a921601 My issue had been resolved by a more careful approach taken by timeSeries. The other option is wholesale deprecation of S4 ... but I won't start that conver

Re: [Rd] methods cbind2 bind_activation disrupts cbind everywhere

2012-09-14 Thread Martin Maechler
> Martin Morgan > on Wed, 12 Sep 2012 15:23:02 -0700 writes: > The methods package ?cbind2 includes the instruction to > use via methods:::bind_activation(TRUE). well, "instruction" only if one wants to magically enable its use for cbind(), rbind() > use via methods:::b

[Rd] methods cbind2 bind_activation disrupts cbind everywhere

2012-09-12 Thread Martin Morgan
The methods package ?cbind2 includes the instruction to use via methods:::bind_activation(TRUE). This changes the default definition of cbind globally, disrupting proper evaluation in packages not using cbind2. Is cbind2 a hold-over from a time when ... could not be used for dispatch? What is a