Dear all,
I am trying to use Rcpp to write some files in C++ for use in R.
Below is an example for a cpp-file (crossp.cpp). Then I use
>sourceCpp("crossp.cpp") in R and the corresponding function is
availabe in R.
Now I have to question related to this worklfow:
1) Is there a way to see the sour
On 30 September 2014 at 13:00, Martin Spindler wrote:
| I am trying to use Rcpp to write some files in C++ for use in R.
Please subscribe to rcpp-devel, and post on that list.
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
__
I have access to a cluster on which I have been supplied with R 3.1.0 which
appears to have been built using the intel compiler tools.
The following minimal Fortran file:
subroutine truth(lind)
logical lind
lind = .TRUE.
end
Compiles thusly:
arcadia> R CMD SHLIB truth.f
On 30/09/2014, 7:41 AM, Barry Rowlingson wrote:
> I have access to a cluster on which I have been supplied with R 3.1.0 which
> appears to have been built using the intel compiler tools.
>
> The following minimal Fortran file:
>
> subroutine truth(lind)
> logical lind
> lind = .
On Tue, Sep 30, 2014 at 12:53 PM, Duncan Murdoch
wrote:
>
> This appears to be user error. According to Writing R Extensions, the
> Fortran type corresponding to R logical is INTEGER, not LOGICAL.
>
Oh yes, a very old and long-standing user error. I assume the CRAN checks
don't check this. Has
On 30/09/2014 8:39 AM, Barry Rowlingson wrote:
On Tue, Sep 30, 2014 at 12:53 PM, Duncan Murdoch
mailto:murdoch.dun...@gmail.com>> wrote:
This appears to be user error. According to Writing R Extensions, the
Fortran type corresponding to R logical is INTEGER, not LOGICAL.
Oh yes,
In S+ and S it was valid to pass logicals to .Fortran, where they got
mapped into the
appropriate bit pattern. (The trouble was that 'appropriate' was
compiled into the program -
so you were locked into our compiler vendor's choice). Passing them
between Fortran
code and C code has always been a
E.g. I am seeing:
dir <- file.path(tempdir(), "test-tar")
dir.create(dir)
setwd(dir)
dir.create("foo", showWarnings = FALSE)
file.create("foo/bar.R")
tar("test.tar", files = "foo/bar.R")
dir.create("untarred")
untar("test.tar", exdir = "untarred")
list.files("
Sounds like a bug to me, at least in documentation. I would say
that it ignores them by accident. I doubt that skipping files is
intended.
The problem appears to be that the 'files' argument to tar() becomes
the 'path' argument to list.files(), and the spec for 'path' is not
a whole lot more ill
I have a question about shallow copies in R. Since R 3.1.0, subsetting
a dataframe with respect to its columns no longer result in deep
copies. This is an amazing change in my opinion. Now, subsetting a
data.frame by rows (or subsetting a matrix by columns or rows) still
does deep copies. In partic
On Tue, Sep 30, 2014 at 2:20 PM, Matthieu Gomez
wrote:
> I have a question about shallow copies in R. Since R 3.1.0, subsetting
> a dataframe with respect to its columns no longer result in deep
> copies. This is an amazing change in my opinion. Now, subsetting a
> data.frame by rows (or subsettin
11 matches
Mail list logo
