From: Philippe Grosjean [EMAIL PROTECTED]
However, I was suprised to learn that the Pipeline Pilot R Collection is
not GPL and is not free (in term of money, i.e., you have to pay
3500$/year to use it). I am not sure, but I think they break the GPL
license here since they use a commercial
,
It is possible to turn stack checking off by setting R_CStackLimit = -1 in
the embedding application: it works for me, so can you please try it?
Brian
On Wed, 19 Apr 2006, A.J. Rossini wrote:
Well, nothing has changed in the issues that I brought up earlier,
except that I can confirm core
connected again).
On 4/19/06, A.J. Rossini [EMAIL PROTECTED] wrote:
It doesn't seem to help. I suspect it is more related to signal
handling changes than the stack. Note that I dropped that from the
subject line for my email which started this thread, but I agree, I
didn't mention signal handing
I should also make it clear -- while I reported non-fatal stack errors
in the first thread, I'm not seeing them any more, just the core dump.
On 4/19/06, A.J. Rossini [EMAIL PROTECTED] wrote:
I'm going to recode the sequence in C tommorow (I'm in Seattle right
now, not Basel, so it's late
I'm pretty sure that we've fixed that problem. (I'm merging 2 different
CL/R trees together, one of which is Cyrus's). An alternative fix patched
R to undo that, but that's not kosher.
best,
-tony
On 4/12/06, Thomas Lumley [EMAIL PROTECTED] wrote:
On Tue, 11 Apr 2006, A.J. Rossini wrote
On 4/11/06, Prof Brian Ripley [EMAIL PROTECTED] wrote:
On Tue, 11 Apr 2006, A.J. Rossini wrote:
I will say this first -- I can't copy/paste the error message from the
screen, so it's being retyped. Errors might occur. SORRY.
I've been experiencing some interesting stack warnings
is being embedded doing anything with
the stack, e.g. some lisp system playing with threads
via manipulating the stack?
D.
A.J. Rossini wrote:
I will say this first -- I can't copy/paste the error message from the
screen, so it's being retyped. Errors might occur. SORRY.
I've been
On 4/12/06, Simon Urbanek [EMAIL PROTECTED] wrote:
On Apr 11, 2006, at 5:34 AM, A.J. Rossini wrote:
I've been experiencing some interesting stack warnings recently
when moving from R 2.2.x to the R 2.3.0 series and the R 2.4.0
series. In particular, I'm getting warnings of Error: C stack
-- Forwarded message --
From: Byron Ellis [EMAIL PROTECTED]
If we wanted to be truly radical we'd just accept that graphics
devices and event loops are just special cases of the connection and
merge the whole thing, thus more-or-less reinventing CLIM. :-)
Eventually, all
the new tar ball.
And I have also been corrected: most of the work on the cross-
compiling tools were in fact done by Brian Ripley.
Kasper
On Oct 18, 2005, at 10:45 AM, A.J. Rossini wrote:
Technically, Jun Yan, based on work and documentation most likely by
Brian Ripley, with Tony
Technically, Jun Yan, based on work and documentation most likely by
Brian Ripley, with Tony prodding Jun. Though I'm sure even that
would be corrected.
Sorry, no clue, as I'm not using R nor Linux at work these days. I'm
sure someone else knows.
On 10/18/05, Kasper Daniel Hansen [EMAIL
it correctly and so works.
I am not sure BTW that lattice_0.12-7 is necessarily compatible with R
2.2.0.
Brian
On Tue, 4 Oct 2005, A.J. Rossini wrote:
R-devel, SVN revision 35729 (this morning, euro-time)
So far, I'm having awful luck with the installWithVers flags.
Recent example
. new.packages() showed
it as new in both 2.1.1 and 2.2.0-beta.
The issue is that installed.packages() has never been taught about
versioned installs, and you might like to take that up with your BioC
colleagues who added the idea.
On Fri, 30 Sep 2005, A.J. Rossini wrote:
In Rdevel, SVN
It might be my settings or improper use -- but if I use the
installWithVers=TRUE flag for update.packages(), I don't seem to get
updates;
and if I use install.packages(new.packages(),installWithVers=TRUE),
it seems to (re-)install identical versions of what I have.
(this is with Rdevel from
14 matches
Mail list logo
