> "RobMcG" == McGehee, Robert <[EMAIL PROTECTED]>
> on Tue, 29 Jul 2008 15:40:37 -0400 writes:
RobMcG> FYI,
RobMcG> I've tried posting the below message twice to the bug tracking
system,
RobMcG> once by email (below), and the second time 5 days later directly to
the
> "RobMcG" == McGehee, Robert <[EMAIL PROTECTED]>
> on Tue, 29 Jul 2008 15:40:37 -0400 writes:
RobMcG> FYI,
RobMcG> I've tried posting the below message twice to the bug tracking
system,
[... r-bugs problems discussed in a separate thread ]
RobMcG> R-devel
Try this workaround
sapply(x, function(x) is.numeric(x))
dt
FALSE
is.numeric is primitive, and primitive functions don't always play well
with [sl]apply.
On Tue, 29 Jul 2008, McGehee, Robert wrote:
FYI,
I've tried posting the below message twice to the bug tracking system,
once by emai
On Wed, 30 Jul 2008, Martin Maechler wrote:
"RobMcG" == McGehee, Robert <[EMAIL PROTECTED]>
on Tue, 29 Jul 2008 15:40:37 -0400 writes:
RobMcG> FYI,
RobMcG> I've tried posting the below message twice to the bug tracking
system,
[... r-bugs problems discussed in a separate thr
> "BDR" == Prof Brian Ripley <[EMAIL PROTECTED]>
> on Wed, 30 Jul 2008 13:29:38 +0100 (BST) writes:
BDR> On Wed, 30 Jul 2008, Martin Maechler wrote:
>>> "RobMcG" == McGehee, Robert <[EMAIL PROTECTED]>
>>> on Tue, 29 Jul 2008 15:40:37 -0400 writes:
>>
RobMcG
I'm using Gnome.
Ben
Prof Brian Ripley wrote:
We have found elsewhere that the need to use XSync is very dependent on
the window manager. What manager were you using?
I'll add the call in any case.
On Tue, 29 Jul 2008, Bill Dunlap wrote:
On Tue, 29 Jul 2008, Ben Bolker wrote:
That
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/
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 pos
On Jul 30, 2008, at 9:45 , 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-suppl
On 30 Jul 2008, at 15:46, Simon Urbanek wrote:
On Jul 30, 2008, at 9:45 , 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 co
On 30 Jul 2008, at 15:18, Kjell Konis wrote:
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
On Jul 30, 2008, at 12:35 , Ernest Turro wrote:
On 30 Jul 2008, at 15:18, Kjell Konis wrote:
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
On Jul 30, 2008, at 12:32 , Ernest Turro wrote:
On 30 Jul 2008, at 15:46, Simon Urbanek wrote:
On Jul 30, 2008, at 9:45 , 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
On 30 Jul 2008, at 18:04, Simon Urbanek wrote:
On Jul 30, 2008, at 12:32 , Ernest Turro wrote:
On 30 Jul 2008, at 15:46, Simon Urbanek wrote:
On Jul 30, 2008, at 9:45 , Ernest Turro wrote:
Dear all,
R on Macports relies on GCC 4.3 to build packages. I find that
packages with shared
On 30 Jul 2008, at 17:58, Simon Urbanek wrote:
On Jul 30, 2008, at 12:35 , Ernest Turro wrote:
On 30 Jul 2008, at 15:18, Kjell Konis wrote:
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
On Jul 30, 2008, at 13:16 , Ernest Turro wrote:
On 30 Jul 2008, at 18:04, Simon Urbanek wrote:
On Jul 30, 2008, at 12:32 , Ernest Turro wrote:
On 30 Jul 2008, at 15:46, Simon Urbanek wrote:
On Jul 30, 2008, at 9:45 , Ernest Turro wrote:
Dear all,
R on Macports relies on GCC 4.3 to
On 30 Jul 2008, at 19:23, Simon Urbanek wrote:
On Jul 30, 2008, at 13:16 , Ernest Turro wrote:
On 30 Jul 2008, at 18:04, Simon Urbanek wrote:
On Jul 30, 2008, at 12:32 , Ernest Turro wrote:
On 30 Jul 2008, at 15:46, Simon Urbanek wrote:
On Jul 30, 2008, at 9:45 , Ernest Turro wrote
On 30 Jul 2008, at 20:25, Simon Urbanek wrote:
On Jul 30, 2008, at 15:13 , Ernest Turro wrote:
On 30 Jul 2008, at 19:23, Simon Urbanek wrote:
On Jul 30, 2008, at 13:16 , Ernest Turro wrote:
On 30 Jul 2008, at 18:04, Simon Urbanek wrote:
On Jul 30, 2008, at 12:32 , Ernest Turro wrot
On Jul 30, 2008, at 15:13 , Ernest Turro wrote:
On 30 Jul 2008, at 19:23, Simon Urbanek wrote:
On Jul 30, 2008, at 13:16 , Ernest Turro wrote:
On 30 Jul 2008, at 18:04, Simon Urbanek wrote:
On Jul 30, 2008, at 12:32 , Ernest Turro wrote:
On 30 Jul 2008, at 15:46, Simon Urbanek wrot
To handle name clashes among packages I wonder if we could
have a namespace setting between exported and not-exported
which is exported but you have to use :: (two dots) to access its
objects. The difference between mandatory two dot and
three dots in this case is that the
exported objects are int
20 matches
Mail list logo
