On Sep 5, 2009, at 2:31 PM, Peter Juhasz wrote:
Reposting from R-help:
Dear R experts,
please excuse me for writing to the mailing list without subscribing.
I have a somewhat urgent problem that relates to R.
I have to process large amounts of data with R - I'm in an
international collaborat
Reposting from R-help:
Dear R experts,
please excuse me for writing to the mailing list without subscribing.
I have a somewhat urgent problem that relates to R.
I have to process large amounts of data with R - I'm in an
international collaboration and the data processing protocol is fixed,
that
Thanks Romain and Barry for help with this. I've written a faux.vignette
function somewhat along the lines of Romain's suggestion.
Roger Koenker
--
View this message in context:
http://www.nabble.com/Viewing-pdfs-from-inst-doc-tp25302477p25310670.html
Sent from the R devel mailing list arc
Allen S. Rout wrote:
On Sep 2, 2009, at 2:53 , Allen S. Rout wrote:
I'm working to automate the building of RPM packages for CRAN &c.
In the process, I'm trying to get a sense of the correct
dependencies.
[...]
In other words, to check properly, I need to treat Suggests and
Imports as D
On Sat, Sep 5, 2009 at 6:15 AM, Andrew Piskorski wrote:
> On Fri, Sep 04, 2009 at 08:39:12AM -0500, Hadley Wickham wrote:
>
>> When developing a package, it's often useful to be able to reload it,
>> without re-installing, re-starting R and re-loading.
>
> Why would you ever need to restart R in su
Yuri,
Based on your brief description, we have already done this with
bigmemory, and the ff package does something very similar but with
emphasis on a wide range of atomic data types and data frame. Unless
you are planning something different from what's been done before, you
shouldn't waste valu
On Fri, Sep 04, 2009 at 08:39:12AM -0500, Hadley Wickham wrote:
> When developing a package, it's often useful to be able to reload it,
> without re-installing, re-starting R and re-loading.
Why would you ever need to restart R in such a situation?
What I do is make the code change in my package
Looking through the archives I found this thread
http://tolstoy.newcastle.edu.au/R/e4/devel/08/02/0347.html
and so I tried
MAKEFLAGS="CFLAGS=-g -O" R CMD SHLIB ...
and this worked great.
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mail
Hello,
At the moment, R-tryEval (src/main/context.c) :
SEXP R_tryEval(SEXP e, SEXP env, int *ErrorOccurred)
would set ErrorOccurred to 1 and return NULL when an error occurs during
the evaluation of e within env, so to know that an error occured, we can
just look at the ErrorOccured value and
I compile some C code using
R CMD SHLIB buggyCode.c --ggdb --O0
I thought the -O0 flag would avoid gdb ~ optimisation problems. But each time I
step through the code in gdb using "n" (next line) the executed line order is
not as expected ("looks" more like a random walk around the expected next
l
10 matches
Mail list logo