similar to: [R] zero-offset matrices (PR#132)

Displaying 20 results from an estimated 7000 matches similar to: "[R] zero-offset matrices (PR#132)"

1999 Mar 02
1
zero-offset matrices
Has anyone written subscripting methods for matrices which are indexed from zero? i.e. functions such as "[.zoffset" and "[<-.zoffset" which would allow, given an appropriate function "zmatrix" "zmatrix" <- function(...) { robj <- matrix(...) class(robj) <- "zoffset" robj } fred <- zmatrix(1:20, 4, 5) fred[0, 4] # would be 17
1998 Jul 10
2
R-beta: R-0.62.2 is released
I have just put R-0.62.2.tgz and R-0.62.1-0.62.2.diff.gz into the FTP area at Auckland. As usual, do not fetch it from there unless absolutely urgent, because of the NZ Internet billing system. The files should get mirrored to the main CRAN site in Vienna tonight and the rest of CRAN within days. [This time I seem to have managed to get the release out on the same date for all core team members
1998 Jul 10
2
R-beta: R-0.62.2 is released
I have just put R-0.62.2.tgz and R-0.62.1-0.62.2.diff.gz into the FTP area at Auckland. As usual, do not fetch it from there unless absolutely urgent, because of the NZ Internet billing system. The files should get mirrored to the main CRAN site in Vienna tonight and the rest of CRAN within days. [This time I seem to have managed to get the release out on the same date for all core team members
1998 Jul 10
2
R-beta: R-0.62.2 is released
I have just put R-0.62.2.tgz and R-0.62.1-0.62.2.diff.gz into the FTP area at Auckland. As usual, do not fetch it from there unless absolutely urgent, because of the NZ Internet billing system. The files should get mirrored to the main CRAN site in Vienna tonight and the rest of CRAN within days. [This time I seem to have managed to get the release out on the same date for all core team members
1998 Jul 30
1
zero-extent matrix crash
Anyone for a little debugging? > matrix(numeric(0),0,0) Floating point exception (core dumped) [I've decided to make a habit of sending bugs that I'm not going to attack right away to R-devel, in case someone might be interested in chipping in and saving the core team the work] -- O__ ---- Peter Dalgaard Blegdamsvej 3 c/ /'_ --- Dept. of Biostatistics
2009 Dec 04
0
(PR#14103) read.csv confused by newline characters in
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --27464147-536455723-1259929222=:18586 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: <alpine.LFD.2.00.0912041222341.18586 at gannet.stats.ox.ac.uk> It's not to do with pushback per
2000 Mar 01
1
Re: Re: R-1.0.0 is released (PR#467)
bhoel@server.python.net (Berthold Höllmann) writes: > Peter Dalgaard BSA <p.dalgaard@biostat.ku.dk> writes: > > > I've rolled up R-1.0.0.tgz a short while ago. > > > I've build R-1.0.0 on my > > >uname -a > Linux pchoel 2.2.14 #3 Mit Jan 5 08:57:39 MET 2000 i686 unknown > > box. Calling "make check" fails with .... > >
2000 Mar 01
1
Re: Re: R-1.0.0 is released (PR#467)
bhoel@server.python.net (Berthold Höllmann) writes: > Peter Dalgaard BSA <p.dalgaard@biostat.ku.dk> writes: > > > I've rolled up R-1.0.0.tgz a short while ago. > > > I've build R-1.0.0 on my > > >uname -a > Linux pchoel 2.2.14 #3 Mit Jan 5 08:57:39 MET 2000 i686 unknown > > box. Calling "make check" fails with .... > >
1999 Jul 08
0
Hack for making old R binaries work after glibc upgrade
Perhaps a bit of a moot point since Martyn now does 6.0 RPM's, but I thought someone might have a use for it, now that I've stumbled across it... $ cat > dummy.c __setfpucw(){} $ gcc -shared -o dummy.so dummy.c $ LD_PRELOAD=$PWD/dummy.so R R : Copyright 1999, The R Development Core Team Version 0.64.2 (July 3, 1999) ... -- O__ ---- Peter Dalgaard Blegdamsvej 3
2004 Nov 04
2
2.0.1 countdown
We plan to a patch release on Nov.15 to fix up various problems that cropped up after the release of R 2.0.0. Daily beta snapshots will be made available until the day of release. Please check if your favourite bugs have been fixed (but notice that since we try hard to keep the patch versions stable, some items may have to wait for the 2.1 release.) Also, please help us with platform testing.
2004 Apr 20
2
Re: [R] Unexpected behaviour of identical (PR#6799)
"Swinton, Jonathan" <Jonathan.Swinton@astrazeneca.com> writes: > # works as expected > > ac <- c('A','B'); > > identical(ac,ac[1:2]) > [1] TRUE > > #but > > af <- factor(ac) > > identical(af,af[1:2]) > [1] FALSE > > Any opinions? Did a cross-check with Splus and it doesn't do that , so I think it
2010 Jun 01
1
strange pvops problem
I compiled the pvops kernel like this : [root@localhost xen-4.0.0]# ls buildconfigs config Config.mk.orig dist extras install.sh Makefile README tools xen build-linux-2.6-pvops_x86_32 Config.mk COPYING docs file linux-2.6-pvops.git messages stubdom unmodified_drivers [root@localhost build-linux-2.6-pvops_x86_32]# make -j2 bzImage
2010 Jun 01
1
strange pvops problem
I compiled the pvops kernel like this : [root@localhost xen-4.0.0]# ls buildconfigs config Config.mk.orig dist extras install.sh Makefile README tools xen build-linux-2.6-pvops_x86_32 Config.mk COPYING docs file linux-2.6-pvops.git messages stubdom unmodified_drivers [root@localhost build-linux-2.6-pvops_x86_32]# make -j2 bzImage
2010 Feb 14
1
NextMethod() example from S Programming by Venables and Ripley (page 78)
S Programming by Venables and Ripley (page 78) has the example listed at the end of this email. However, I get the following error when I try the example. I don't understand the descriptions of NextMethod on its help page. Could somebody let me know how to fix the error of this example? > test(x) c1 c2 Error in NextMethod() : no method to invoke Calls: test -> test.c1 -> NextMethod
2012 Oct 17
1
Do *not* pass '...' to NextMethod() - it'll do it for you; missing documentation, a bug or just me?
Hi, although I've done S3 dispatching for more than a decade now, I think I managed to overlook/avoid the following pitfall when using NextMethod(): If you explicitly pass argument '...' to NextMethod(), you will effectively pass those argument twice to the "next" method! EXAMPLE: foo0 <- function(...) UseMethod("foo0"); foo1 <- function(...)
2004 Oct 28
1
Another problem with next method
I have another problem with NextMethod. Not sure if its related to the last problem. In this example, we have a generic called ff with methods for AsIs and test classes. We call the generic with an object of AsIs class. The corresponding method adds 1 to it and then changes the class to test followed by issuing a NextMethod. However, that results in this error (using R 2.0.0, 2004-10-04
2018 Feb 22
0
How to modify dots and dispatch NextMethod
2018-02-22 12:39 GMT+01:00 Tomas Kalibera <tomas.kalibera at gmail.com>: > On 02/22/2018 12:07 PM, I?aki ?car wrote: >> >> 2018-02-22 10:29 GMT+01:00 Tomas Kalibera <tomas.kalibera at gmail.com>: >>> >>> The example is invoking NextMethod via an anonymous function, which is >>> not >>> allowed (see documentation for NextMethod).
2018 Feb 22
2
How to modify dots and dispatch NextMethod
The example is invoking NextMethod via an anonymous function, which is not allowed (see documentation for NextMethod). Normally one gets a runtime error "'NextMethod' called from an anonymous function", but not here as the anonymous function is called via do.call. I will fix so that there is a runtime error in this case as well, thanks for uncovering this problem. I
1997 Dec 02
1
R-alpha: NextMethod in 0.50-a4
I am encountering difficulty with NextMethod in 0.50-a4. We created a class of groupedData objects which are data.frames with additional attributes. The most important attribute is a formula describing roles of some of the variables in the experimental design. The class of such objects ends in "groupedData", "data.frame". The print method for the groupedData class simply
2018 Feb 22
2
How to modify dots and dispatch NextMethod
On 02/22/2018 12:07 PM, I?aki ?car wrote: > 2018-02-22 10:29 GMT+01:00 Tomas Kalibera <tomas.kalibera at gmail.com>: >> The example is invoking NextMethod via an anonymous function, which is not >> allowed (see documentation for NextMethod). > Thanks for your response. I definitely missed that bit. > >> Normally one gets a runtime >> error