Hi all,
[EMAIL PROTECTED] wrote:
>
> Consider my guesstimate:
> For 99% of all R users, the amount of time they need working
> pretty intensely with R before they find a bug in it,
> is nowadays more than three years, and maybe even much more
> -- such as their lifetime :-)
Perhaps I belong to
Hi,
I can't load XML_1.4-0.zip in last R devel (Windows):
R version 2.5.0 Under development (unstable) (2007-01-05 r40386)
Copyright (C) 2007 The R Foundation for Statistical Computing
ISBN 3-900051-07-0
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redis
What Peter & Vladimir refers to are the causes of problems - adding
"-Wall" to all of CFLAGS, CXXFLAGS, FFLAGS should spot some of them.
I did know of one case of uninitialised variable causing a crash -
doing "FILE *file; close(file);" crashes with gcc but not with sun
workshop (sun workshop imp
The problem with the misuse of 'long' in package 'subselect' was reported
to Mr Cadima in February 2005 (along with a number of other package
maintainers).
On Fri, 5 Jan 2007, Vladimir Dergachev wrote:
> On Friday 05 January 2007 12:10 pm, Peter Dalgaard wrote:
>> Hin-Tak Leung wrote:
>>> I go
On Friday 05 January 2007 12:10 pm, Peter Dalgaard wrote:
> Hin-Tak Leung wrote:
> > I got the same error with 64-bit R 2.4.1 on FC6 x86_64, and 32-bit
> > R 2.4.1 on the same machine is okay. There is definitely something wrong
> > with your code.
> >
> > I would suggest fixing all the compier war
Hin-Tak Leung wrote:
> I got the same error with 64-bit R 2.4.1 on FC6 x86_64, and 32-bit
> R 2.4.1 on the same machine is okay. There is definitely something wrong
> with your code.
>
> I would suggest fixing all the compier warnings - there are piles of
> them about uninitialized variables, and a
I got the same error with 64-bit R 2.4.1 on FC6 x86_64, and 32-bit
R 2.4.1 on the same machine is okay. There is definitely something wrong
with your code.
I would suggest fixing all the compier warnings - there are piles of
them about uninitialized variables, and about doing comparison
between si
Hello,
I would appreciate *any* ideas on this problem. I'm the maintainer of a
package ("subselect"), which on CRAN's Daily Package Checks is OK on all
flavours of R, except r-devel Linux x86_64, where there is a "memory not
mapped" segfault with the very first example that is tried out (outp
Hi Erik,
Erik van Zijst <[EMAIL PROTECTED]> writes:
> Hi Martin,
>
> Your approach of bolting a webservices layer on top of R is a really
> nice (and quite natural) thing to do.
[...]
> As you already suggested, webservices are fairly expensive with their
> HTTP and XML-parsing, making it less su
Vladimir Dergachev wrote:
>>Using pipes or shared memory to pass things around to other processes on
>>the same box is very fast indeed, but if we base our design around
>>something like RServe which uses TCP it could be significantly slower.
>>Our R-based system will be running scripts in response
Jeffrey Horner wrote:
> I haven't looked at RServe in awhile, but I think that it fires up an R
> interpreter in response to a client request and then sticks around for
> the same client to serve it additional requests. The question is how
> does it manage all the R interpreters with varying dem
On Mon, 1 Jan 2007, Duncan Temple Lang wrote:
> Kurt Hornik wrote:
>>> Duncan Temple Lang writes:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>
>>> Prof Brian Ripley wrote:
I've added to R-devel the ability to use download.file() and url() to
https: URLs, *only* if --in
Hi Martin,
Your approach of bolting a webservices layer on top of R is a really
nice (and quite natural) thing to do.
I appreciate your early announcement in response to our thread and I'd
very much like to be kept in the loop of future announcements, so please
add my address to your list.
As yo
13 matches
Mail list logo
