Re: [Rd] UnauthorizedAccessException in R(D)COM

2005-04-17 Thread Prof Brian Ripley
This is the wrong list for R(D)COM, which is not part of R. It has its own support list. Almost all readers of this list have no idea what the MicroSoft jargon you are using means. See the `home page' http://cran.r-project.org/contrib/extra/dcom/RSrv135.html for more details. On Mon, 18 Apr 2005

[Rd] UnauthorizedAccessException in R(D)COM

2005-04-17 Thread WeiQiang . Li
Dear friends, I am trying to create a web application to produce some statistical result using R. In order to avoid high CPU usage of web server caused by R, I have to create an ASP.NET web service in another server to involve R. But I am facing the unauthorizedAccessExcepti

[Rd] recent spam on mailing lists

2005-04-17 Thread Martin Maechler
Probably not many of you have noticed, since I assume you have your own active spam filters: But we have recently (first time on Friday April 15) had problems with spam filtering on our mail server. The spamassassin daemon (spamd) has "died" for no apparent reason, and hence the mail has been pass

[Rd] UnauthorizedAccessException in R(D)COM

2005-04-17 Thread WeiQiang . Li
Dear friends, I am trying to create a web application to produce some statistical result using R. In order to avoid high CPU usage of web server caused by R, I have to create an ASP.NET web service in another server to involve R. But I am facing the unauthorizedAccessException

[Rd] density() with weights

2005-04-17 Thread Adrian Baddeley
Hello - Recently I needed to compute kernel density estimates for a vector of observations x with given weights w instead of the conventional equal weights w[i] = 1/length(x). AFAIK, the existing code in 'base' does not accept weights. It wasn't hard to modify the C and R code for `density' i

Re: [Rd] RFC: hexadecimal constants and decimal points

2005-04-17 Thread Prof Brian Ripley
On Sun, 17 Apr 2005, Jan T. Kim wrote: On Sun, Apr 17, 2005 at 12:38:10PM +0100, Prof Brian Ripley wrote: These are some points stimulated by reading about C history (and related in their implementation). 1) On some platforms as.integer("0xA") [1] 10 but not all (not on Solaris nor Windows). We do

Re: [Rd] RFC: hexadecimal constants and decimal points

2005-04-17 Thread Jan T. Kim
On Sun, Apr 17, 2005 at 12:38:10PM +0100, Prof Brian Ripley wrote: > These are some points stimulated by reading about C history (and > related in their implementation). > > > 1) On some platforms > > >as.integer("0xA") > [1] 10 > > but not all (not on Solaris nor Windows). We do not define w

Re: [Rd] RFC: hexadecimal constants and decimal points

2005-04-17 Thread Gabor Grothendieck
On 4/17/05, Prof Brian Ripley <[EMAIL PROTECTED]> wrote: > These are some points stimulated by reading about C history (and > related in their implementation). > > 1) On some platforms > > > as.integer("0xA") > [1] 10 > > but not all (not on Solaris nor Windows). We do not define what is > allo

[Rd] RFC: hexadecimal constants and decimal points

2005-04-17 Thread Prof Brian Ripley
These are some points stimulated by reading about C history (and related in their implementation). 1) On some platforms as.integer("0xA") [1] 10 but not all (not on Solaris nor Windows). We do not define what is allowed, and rely on the OS's implementation of strtod (yes, not strtol). It seems

Re: [Rd] Using lengthgets() correctly (was SET_LENGTH)

2005-04-17 Thread Prof Brian Ripley
I assume this is not true of your actual example, but the sample code allocates a character matrix and calls INTEGER() on it. Ouch! On Sun, 17 Apr 2005, Prof Brian Ripley wrote: If you use R not the S-compatibility macros you will be less likely to confuse yourself. The definition is (analogous

Re: [Rd] Using lengthgets() correctly (was SET_LENGTH)

2005-04-17 Thread Prof Brian Ripley
If you use R not the S-compatibility macros you will be less likely to confuse yourself. The definition is (analogous to realloc) Rdefines.h:#define SET_LENGTH(x, n) (x = lengthgets(x, n)) so x is changed and needs to be reprotected. [I don't know that SET_LENGTH *is* part of the API: it is no