On Sun, May 30, 2010 at 4:31 PM, Duncan Murdoch
wrote:
> As far as I know, there is none. It is reserved simply because it follows
> the pattern of "..n". It would not be hard to make ..0 specially unreserved,
> but what would be the point?
Here is the case I had in mind.
The gsubfn function in
On 30/05/2010 3:44 PM, Gabor Grothendieck wrote:
Note that ?Reserved lists ..1, ..2, to ..9 but does not list ..0.
Which version are you looking at? Mine says "‘..1’, ‘..2’ etc," In fact,
the code just looks for the pattern of two dots followed by something
that can be converted to a long;
Note that ?Reserved lists ..1, ..2, to ..9 but does not list ..0.
Also, why is it reserved? What is the future intended use?
On Sun, May 30, 2010 at 3:40 PM, Duncan Murdoch
wrote:
> On 30/05/2010 3:13 PM, Gabor Grothendieck wrote:
>>
>> This function call returns 3 but should return 32. ..0 ha
On 30/05/2010 3:13 PM, Gabor Grothendieck wrote:
This function call returns 3 but should return 32. ..0 has no special
significance in R as far I know yet it seems to be acting as if it
were ..1 . Comments?
Actually, ..0 is a reserved symbol. (This is just barely documented in
the R Lang
This function call returns 3 but should return 32. ..0 has no special
significance in R as far I know yet it seems to be acting as if it
were ..1 . Comments?
> ff <- function(..0, ...) ..0
> ff(32, 3)
[1] 3
> R.version.string
[1] "R version 2.11.0 Patched (2010-04-26 r51822)"
> win.version()
[1
