OK thanks. Just FYI the same thing happens with R version 2.5.0
devel (2006-09-07 r39185).
Best,
H.
Peter Dalgaard wrote:
> [EMAIL PROTECTED] writes:
>
>
>> Hi,
>>
>> On Windows, 'install.packages(,type="source")' displays the same output
>> than 'R CMD INSTALL --help' and doesn't install anyt
[EMAIL PROTECTED] writes:
> Hi,
>
> On Windows, 'install.packages(,type="source")' displays the same output
> than 'R CMD INSTALL --help' and doesn't install anything...
Yes. The culprit is
r39127 | urbaneks | 2006-09-05 2
Hi,
On Windows, 'install.packages(,type="source")' displays the same output
than 'R CMD INSTALL --help' and doesn't install anything...
This is with R version 2.4.0 alpha (2006-09-06 r39158).
> install.packages('cat',type='source')
trying URL 'http://cran.cnr.Berkeley.edu/src/contrib/cat_0.0-6.
Anil Maliyekkel wrote:
> [snip]
>
> Going back to the original partial replacement problem, is there
> anyway to turn off partial matching, or to selectively apply exact
> matching when trying to access a single element? I can get the
> desired single element match using the convoluted synt
Or more in the spirit of method dispatch, and to get some insight into
why this design decision is not a bug:
> setClass("test",representation(x="character"))
[1] "test"
>
> setMethod("[",
+ signature(x="test", drop="missing"),
+ function(x, i, j, ..., drop) {
+
Or more in the spirit of method dispatch, and to get some insight into
why this design decision is not a bug:
> setClass("test",representation(x="character"))
[1] "test"
>
> setMethod("[",
+ signature(x="test", drop="missing"),
+ function(x, i, j, ..., drop) {
+
> > I can get the
> > desired single element match using the convoluted syntax D["ABC"]
> > [[1]] and perform partial replacement operations on a new column.
> > However, it would be nice to have single element access operator that
> > does exact matching.
>
> It wouldn't fix the bug, and we are r
On Tue, 5 Sep 2006, Anil Maliyekkel wrote:
> This problem does not appear when the following is done
>
> > D = list(ABCD=2:1)
> > D$ABC[]=c(3,4)
> > D
> $ABCD
> [1] 2 1
>
> $ABC
> [1] 3 4
>
>
> It appears to be a sequence specific bug for the $ operator, which
> might explain why it did not occur
Try this:
> setClass("test",representation(x="character"))
[1] "test"
> setMethod("[","test",function(x,i,j,...,drop) {
+print(i)
+if (missing(drop)) drop <- TRUE
+print(drop)
+ })
[1] "["
> a = new("test",x="fred")
> a[1]
[1] 1
[1] TRUE
On 9/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED
Patricia Bautista wrote:
> Hi everybody,
>
> Does anybody know where I can find documentation about
> file gram.y?. What I need to do is related to the
> parse tree. I need the parse tree of a R user defined
> function for being used by a c++ function. Briefly, I
> have a C++ function that is use
Full_Name: John Verzani
Version: 2.4.0 alpha (2006-09-05 r39134)
OS: linux, gentoo 2.6.17
Submission from: (NULL) (163.238.43.26)
When extending the "[" method to a new S4 class, the default value for the drop
argument is not being found. Here is a small example:
setClass("test",representation(x
On 9/8/2006 10:03 AM, Patricia Bautista wrote:
> Hi everybody,
>
> Does anybody know where I can find documentation about
> file gram.y?.
It's input to bison (or yacc). You could read bison documentation to
find what it does. I don't think there is any documentation for it
other than that a
Hi everybody,
Does anybody know where I can find documentation about
file gram.y?. What I need to do is related to the
parse tree. I need the parse tree of a R user defined
function for being used by a c++ function. Briefly, I
have a C++ function that is used to generate random
numbers from a spe
>>> Balaji S. Srinivasan stanford.edu> writes:
Balaji> I know the topic of drop=TRUE/FALSE has been
Balaji> discussed quite a bit,
{ indeed and often enough by great minds so that at one point in time
newcomres could believe it was not worth the pain to take it up again ...
14 matches
Mail list logo
