Hi
Brief synopsis:
I am having a rather peculiar problem regarding a C++ library. It
seems that functions from this library behave differently when
compiled using R as opposed to being compiled directly from the
command line. The problem is only seen on the amd64 platform (using
gcc 4.0.2
Juan Santiago Ramseyer <[EMAIL PROTECTED]> writes:
> SYSTEM:
> --
> CPU: AMD64
> MOTHERBOARD: ASUS
> OS: FEDORA CORE 5 i64_86
>
> R SESSION:
> --
> > teste<-list(a=c(1,2,3,4),b=c(2,4,6,8))
> > teste
> $a
> [1] 1 2 3 4
>
> $b
> [1] 2 4 6 8
>
> > de(teste)
> *** buf
You mention 'float' repeatedly. A %f argument in Rprintf (and printf)
refers to a _double_. Given how little you have shown us it has to be
entirely guesswork, but is cel.GetIntensity(1) perhaps a float? If so
what happens is I believe undefined and compiler-specific. (Normally
headers forc
Prof Ripley (and others):
Thank you very much for the idea of the casting problems inside
Rprintf. Unfortunately that did not work. I have now trimmed
everything to a simple example, see below.
The cel methods are indeed defined as floats respectively integers like
class FusionCELData
{
p
Dear R developers,
it seems the stack checking issue with embedded applications is not fully
resolved, yet. The problem arises, when multiple threads are involved. I.e.
the case, where R is run in a separate thread of the main application. In
this case, the call to (unix/system.c)
R_CStack
