From kjell.konis at epfl.ch  Wed Jul 30 16:18:11 2008
From: kjell.konis at epfl.ch (Kjell Konis)
Date: Wed, 30 Jul 2008 16:18:11 +0200
Subject: [Rd] R, Macports and C++ streams
In-Reply-To: <37E1D80F-D1CB-4B4B-80B1-DDBDB0EF43BD@ic.ac.uk>
References: <37E1D80F-D1CB-4B4B-80B1-DDBDB0EF43BD@ic.ac.uk>
Message-ID: <D5AE68F5-E80A-4E84-8988-039A3DF3A97F@epfl.ch>

I found this in Writing R Extensions:

"Using C++ iostreams, as in this example, is best avoided. There is no  
guarantee that the output will appear in the R console, and indeed it  
will not on the R for Windows console. Use R code or the C entry  
points (see Printing) for all I/O if at all possible."

That is, use Rprintf() instead. The fact that your code works with one  
version of gcc and not another can probably be chalked up to  
coincidence.

Kjell

On Jul 30, 2008, at 3:45 PM, Ernest Turro wrote:

> Dear all,
>
> R on Macports relies on GCC 4.3 to build packages. I find that
> packages with shared objects that use C++ streams crash R if they're
> compiled using Macports' gcc43, but work fine if compiled in exactly
> the same way using Apple-supplied GCC 4.2. Has anyone here had the
> same issue/know what is causing this problem?
>
> Thanks,
>
> Ernest
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel



[Rd] R, Macports and C++ streams
Kjell Konis