On Apr 29, 2010, at 6:25 AM, Prof Brian Ripley wrote:
> On Thu, 29 Apr 2010, Murray Efford wrote:
>
>> Peter's solution works perfectly. Thanks. Maybe this should be standard.
>
> It is for now, but the intention is to use the more general solution of
> texi2dvi.
>
Thanks, Brian.
I'm not ac
Felix Andrews nfrac.org> writes:
>
> x <- seq(as.POSIXct("2000-01-01"), by = "days", length = 20)
>
> cut(x, breaks = 3)
> # Error in `levels<-.factor`(`*tmp*`, value = character(0)) :
> # number of levels differs
>
> cut(as.Date(x), breaks = 3)
> # Error in `levels<-.factor`(`*tmp*`, value
Hi,
All Japanese encoding was all right if fixed the following.
--- R-2.11.0.orig/src/library/tcltk/src/tcltk.c 2010-03-31
07:10:02.0 +0900
+++ R-2.11.0.work/src/library/tcltk/src/tcltk.c 2010-04-29
23:48:55.0 +0900
@@ -349,7 +349,7 @@
elem = Tcl_NewObj();
Dear UseR,
I get an error when I run "R CMD check" on my .tar.gz file package,
and I don't understand why since I don't obtain any error with "R CMD
check" on the package directory. Do you have any idea ?
$ sudo ./R-2.11.0/bin/R CMD check eqtl_1.1.tar.gz
and
$ sudo ./R-2.11.0/bin/R CMD --check
On 29.04.2010 17:39, Hamid Khalili wrote:
Dear UseR,
I get an error when I run "R CMD check" on my .tar.gz file package,
and I don't understand why since I don't obtain any error with "R CMD
check" on the package directory. Do you have any idea ?
$ sudo ./R-2.11.0/bin/R CMD check eqtl_1.1.ta
The R docs say that there are two methods that the C programmer can
allocate memory, one where R automatically frees the memory on
return from .C/.Call, and the other where the user takes responsibility
for freeing the storage. Both methods involve using R-provided
functions.
What happens when the