Section 1.1.3 of the "R-exts" manual currently refers to "imports or
importFrom directives" where it means to say "import or importFrom
directives". Results of a diff between R-exts.texi at SVN revision
76864 and a corrected version are copied below.
*** R-exts.texi Mon Jul 22 14:41:19 2019
---
Here's the surprising behavior:
x <- 1L
xx <- as(x, "numeric")
class(xx)
## [1] "integer"
It occurs because the call to `as(x, "numeric")` dispatches the coerce
S4 method for the signature `c("integer", "numeric")`, whose body is
copied in below.
function (from, to = "numeric", s
On Dec 19, 2015, at 3:32 AM, Martin Maechler wrote:
>> Martin Maechler
>>on Sat, 12 Dec 2015 10:32:51 +0100 writes:
>
>> John Chambers
>>on Fri, 11 Dec 2015 10:11:05 -0800 writes:
>
>>> Somehow, the most obvious fixes are always back-incompatible these days.
>>> The exam
On Tue, Jan 5, 2016 at 1:31 AM, Martin Maechler
wrote:
>>>>>> Josh O'Brien
>>>>>> on Mon, 4 Jan 2016 16:16:51 -0800 writes:
>
> > On Dec 19, 2015, at 3:32 AM, Martin Maechler stat.math.ethz.ch> wrote:
>
> >>>&g
hods base
loaded via a namespace (and not attached):
[1] tools_3.3.0
Cheers,
Josh O'Brien
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
The "R-admin" manual describes how to build R from outside of the
top-level source directory on a *NIX machine
(http://cran.r-project.org/doc/manuals/r-release/R-admin.html#Simple-compilation),
but it makes no analagous mention of a way to do so under Windows.
Since the build process in Windows is
My question:
On Windows, R's system() command prepends several directories to those
in the Windows Path variable.
>From ?system
The search path for 'command' may be system-dependent: it will
include the R 'bin' directory, the working directory and the
Windows system directories be
On Mon, May 18, 2015 at 10:29 AM, Josh O'Brien wrote:
> My question:
>
> On Windows, R's system() command prepends several directories to those
> in the Windows Path variable.
>
> From ?system
>
> The search path for 'command' may be system-
Hello,
The second paragraph of Chapter 2: .Internal vs .Primitive of R-ints
uses axis() as an example of a function that uses .Internal(). Here's
the quote:
> Functions using .Internal() wrapped in a closure are in general preferred as
> this ensures
> standard handling of named and default argu
>Say I have argnames <- c("a", "b", "c").
>From that I want to construct the equivalent of alist(a=, b=, c=).
Here's a one liner that'll do that for you:
argnames <- letters[1:3]
setNames(rep(list(bquote()), length(argnames)), argnames)
- Josh
--
View this message in context:
http://r.78969
Hello,
Apparently thanks to improvements to the R parser, this example from
section 6.1 of the R Language Definition no longer holds.
> deparse(quote(c(1, 2)))
[1] "c(1, 2)"
> deparse(1:2)
[1] "c(1, 2)"
Even running R-2.14.2, I get instead
> deparse(1:2)
[1] "1:2"
_
Hello,
Doing typeof() on an object appears to reset the "named" field in its
sxpinfo header to 2, which can change the way that subsequent
subassignment operations are carried out:
X <- 1:5e7
.Internal(inspect(X))
# @4eeb0008 13 INTSXP g0c7 [NAM(1)] (len=5000, tl=0) 1,2,3,4,5,...
system.time
Vitalie Spinu wrote
> Hi,
>
>f1 <- function(){
>browser()
>print("aaa")
>}
>
>f2 <- function(){
>a <- 12
>eval(envir = parent.frame(),
> bquote({
>b <- .(a)
>}))
>}
>
>
> Now do,
>
> f1()
>
> and enter
13 matches
Mail list logo
