Witold Eryk Wolski wrote:
Dear developers.
Have spend just 1 h searching for a bug in a new version of a new
version of a package.
I was getting a segfault all the time. "Funny" thing - there was no
error neither in the S nor in the C code.
To solve the problem I had to delete the .Rdata file!
This just means that R doesn't currently do anything complicated when you
ask for a pointer to the data in an R vector object. But that doesn't
matter; the behavior of REAL etc doesn't depend on that.
Note that INTEGER, REAL, etc just give you pointers of type int *, double *,
etc. It's up to you
On Mon, 31 Jan 2005, Prof Brian Ripley wrote:
This is covered, copiously, in the examples in `Writing R Extensions'.
Hint: search for coerceVector.
I see. I thought that INTEGER and its relatives did coercion too, but now
I see that is not stated anywhere.
Eg. REAL is first used in "Writing R E
On Mon, 31 Jan 2005, Barry Rowlingson wrote:
as I would expect. I thought that if the vectors in the list could be
regarded as integer vectors, they would be coerced appropriately, but
apparently not. Is there any way I can tell R to regard them as integer
vectors?
Change:
.Call("printlst", li
On Mon, 31 Jan 2005, Faheem Mitha wrote:
[Forwarding to r-devel.]
Dear People,
Here is something I do not understand. Consider
...
This is covered, copiously, in the examples in `Writing R Extensions'.
Hint: search for coerceVector.
as I would expect. I thought that if the vectors in the list coul
as I would expect. I thought that if the vectors in the list could be
regarded as integer vectors, they would be coerced appropriately, but
apparently not. Is there any way I can tell R to regard them as integer
vectors?
Change:
.Call("printlst", list(c(1,2),c(3,4)))
To:
.Call("printlst", list
[Forwarding to r-devel.]
Dear People,
Here is something I do not understand. Consider
*
foo.cc
*
#include
#include
#include
using std::cout;
using std::endl;
extern "C"
{
SEXP printlst(SEXP lst);
}
This is a multi-part message in MIME format.
--=_NextPart_000_1107183070_B78506032.R82506026
Content-Type: text/plain;
charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
eManager Notification *
The following mail was blocked since it contains sensi
Which version of R is this? I think it has been corrected a while ago
in R-patched and R-devel. Do see the posting guide
On Sun, 30 Jan 2005, Paul Roebuck wrote:
Section 3.5.3 The call stack (pg 23 of R-lang.pdf)
...the computation the the currently active environment...
^^
