On 2010-05-30 15:33, Prof. John C Nash wrote:
A few days ago on R-help I asked about a cross-platform timeout version of
readline().
Some suggestions, but only partial joy so far. I can get the Gnu bash 'read -t
...' to
work in Windows by using the 'bash -c ' construct, but then R's system()
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
A few days ago on R-help I asked about a cross-platform timeout version of
readline().
Some suggestions, but only partial joy so far. I can get the Gnu bash 'read -t
...' to
work in Windows by using the 'bash -c ' construct, but then R's system()
function does not
seem to allow this to pass thr
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
Hi,
Sure. I could and I would provide a patch. Since this is more of a "nice
to have", I wanted to first find out whether others would find it
useful, and also if such a patch would have chances to get accepted by
one of R-core members.
Sometimes patches I or others provide upfront are not a
John,
Thank your for the explanation!
Claudia
--
Claudia Beleites
Dipartimento dei Materiali e delle Risorse Naturali
Università degli Studi di Trieste
Via Alfonso Valerio 6/a
I-34127 Trieste
phone: +39 0 40 5 58-37 68
email: cbelei...@units.it
__
Claudia,
Your S3 methods will be selected for objects from "hyperSpec", but not
for S4 classes that inherit from that class (that have
contains="hyperSpec" in their definition).
The S3 method dispatch has been fixed to recognize S4 classes that
inherit from an S3 class, "foo3" in my example.
Dear all,
thank your for this discussion - I had been wondering how to get the completion
with my S4 class, but it didn't bother me enough to dig into things.
The workaround/hack that *does* work now, I believe, is to insert a
dummy S3 class into the mix and define the S3 .DollarNames method
Hi Romain,
not that I have any authority here, but wouldn't your suggestion (which
I think could be very useful) be more powerful if it were accompanied by
a patch that could be applied to the R sources?
Best wishes
Wolfgang Huber
EMBL
http://www.embl.de/research/units/genome_biology/huber
12 matches
Mail list logo
