G'day,
I'm trying to build R using the code from SVN. I am able to successfully
build the source from here:
http://cran.r-project.org/src/base/R-2/R-2.15.2.tar.gz
However, when building the code checked out from SVN (either from 2.15.2
tag, or the trunk) I get the following error:
Error:
Hi Brian,
I appreciate your clarifications. I am sending this reply to the
R-devel, as per you suggestion.
As mentioned in my post, I have no prior experience with this R function
and logically, I looked up its help page, which states:
Conventionally the domain for *R* warning/error messages
On 13-02-03 9:52 PM, Jonathon Love wrote:
G'day,
I'm trying to build R using the code from SVN. I am able to successfully
build the source from here:
http://cran.r-project.org/src/base/R-2/R-2.15.2.tar.gz
However, when building the code checked out from SVN (either from 2.15.2
tag, or the
On 04/02/2013 11:14, Florent Angly wrote:
Hi Brian,
I appreciate your clarifications. I am sending this reply to the
R-devel, as per you suggestion.
As mentioned in my post, I have no prior experience with this R function
and logically, I looked up its help page, which states:
Conventionally
On 04/02/13 23:47, Duncan Murdoch wrote:
Probably, but if you want help you're going to need to give some more
information first, such as what exactly you installed from SVN, what OS
you are using, what target you tried to build, and anything else
necessary so that a potential helper can
Well, if all else fails read the manual:
The PDF documentation (including doc/NEWS.pdf) and building vignettes
needs tex and latex, or pdftex and pdflatex. We require LaTeX version
2005/12/01 or later (for UTF-8 support). Building PDF package manuals
(including the R reference manual) and
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
On 04/02/2013 12:20 PM, Josh O'Brien wrote:
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)
Thanks, I'll replace that example with this one:
On 5 February 2013 at 01:27, Jonathon Love wrote:
| On 04/02/13 23:47, Duncan Murdoch wrote:
| Probably, but if you want help you're going to need to give some more
| information first, such as what exactly you installed from SVN, what OS
| you are using, what target you tried to build, and
## the following is a dream: add some sugar syntax to allow for
contracts with teeth (in and out checking)
is.positive - function(x) (all(x0))
exponentiate - function( x ::is.data.frame , exponent ::is.numeric
is.positive) :: is.vector is.numeric {
x$base :: is.positive## error
Ivo,
Have you looked at the
TypeInfohttp://www.bioconductor.org/packages/2.12/bioc/html/TypeInfo.htmlBioConductor
package by Gentleman and Temple Lang?
I don't use it myself and can't speak to its current state, but from its
description, and having talked to one of its authors (who, for full
Ivo,
You might be interested in my lambda.r package which provides syntax (using the
%::% operator) for type constraints. Given a function with n arguments, the
type constraint requires n + 1 types, as the last type listed is the return
type. Lambda.r also provides syntax for specifying any
hi brian---interesting and very impressive. is it possible to move
everything into one definition and/or to chain multiple conditions?
exponentiate(x, exponent) %::% data.frame : c(numeric,allpositive) :
integer %as% {
x %has% base ## my invention, since this is not checked, and R is
not
On 05/02/13 00:02, Prof Brian Ripley wrote:
On 04/02/2013 11:14, Florent Angly wrote:
Hi Brian,
I appreciate your clarifications. I am sending this reply to the
R-devel, as per you suggestion.
As mentioned in my post, I have no prior experience with this R function
and logically, I looked
Ivo,
If you don't like the multipart function syntax you can write a single
definition. Personally I prefer this as it isolates data management logic and
control flow from model/application logic. There are duck typing operators that
you can use in the guard similar to the syntax you wrote.
15 matches
Mail list logo
