On 26/07/2012 00:37, Hiroyuki Kawakatsu wrote:
hi,
there appears to be a bug in r-devel (r59963)
src/library/graphics/R/pie.R, line 62
P <- t2xy(seq.int(x[i], x[i + 1], n))
meant to be
P <- t2xy(seq.int(x[i], x[i + 1], length.out=n))
?
discovered when running demo(graphics). si
On 25 July 2012 at 18:46, Dirk Eddelbuettel wrote:
|
| On 25 July 2012 at 15:56, Hadley Wickham wrote:
| | Hi all,
| |
| | Recently, when compiling R packages containing C code, I've started
| | getting the following error:
| |
| | * installing to library ‘/Users/hadley/R’
| | * installing *sou
On 25 July 2012 at 15:56, Hadley Wickham wrote:
| Hi all,
|
| Recently, when compiling R packages containing C code, I've started
| getting the following error:
|
| * installing to library ‘/Users/hadley/R’
| * installing *source* package ‘appdirs’ ...
| ** Creating default NAMESPACE file
| ** l
hi,
there appears to be a bug in r-devel (r59963)
src/library/graphics/R/pie.R, line 62
P <- t2xy(seq.int(x[i], x[i + 1], n))
meant to be
P <- t2xy(seq.int(x[i], x[i + 1], length.out=n))
?
discovered when running demo(graphics). simpler example
is
pie(rep(1, 3), col=rainbow(3), ra
On Jul 24, 2012, at 4:39 PM, Bert Gunter wrote:
Folks:
Herein is a suggestion for a little R convenience function mainly to
obtain unevaluated ... function arguments. It arose from a query on
R-help on how to get these arguments. The standard (I think) idiom to
do this is via
match.call(expan
Hi all,
Recently, when compiling R packages containing C code, I've started
getting the following error:
* installing to library ‘/Users/hadley/R’
* installing *source* package ‘appdirs’ ...
** Creating default NAMESPACE file
** libs
*** arch - i386
gcc -arch i386 -std=gnu99
-I/Library/Frameworks
Folks:
Herein is a suggestion for a little R convenience function mainly to
obtain unevaluated ... function arguments. It arose from a query on
R-help on how to get these arguments. The standard (I think) idiom to
do this is via
match.call(expand.dots=FALSE)$...
However, Bill Dunlap pointed out
Thanks Duncan I was able to find the offending characters in the Rd files.
I'll try latin1 for the data.frame (UTF-8 was obviously not the right
answer for that.)
One thing I was very happy for was that the package just works, not too
shabby since it was orginally built
under 1.9.
Thanks for yo
On 12-07-25 3:24 AM, steven mosher wrote:
Thank Dr. Ripley.
When I read the instructions
" If the DESCRIPTION file is not entirely in ASCII it should contain an ‘
Encoding’ field specifying an encoding. This is used as the encoding of the
DESCRIPTION file itself and of the R and NAMESPACE file
Thank Dr. Ripley.
When I read the instructions
" If the DESCRIPTION file is not entirely in ASCII it should contain an
Encoding field specifying an encoding. This is used as the encoding of the
DESCRIPTION file itself and of the R and NAMESPACE files, and as the
default encoding of .Rd files.
10 matches
Mail list logo