Re: [Rd] Call R From VC++

Shilpi, shilpi harpavat wrote: > I want to write an independent C++ application that > can call any R functions and output it as an > c++object. > I tried to use The documentation for Linking R DLL > with VC++ But with no success. > When I link R.dll it says Invalid or

[Rd] Questions on how to handle R objects in C

Hello, I have a question on how to handle R objects in C. I have spent a lot of time on it but I still can not figure it out. My situation is as following. I have already had C++ code for a genetic algorithm. The genetic algorithm need function evaluations. And the function I am going to use i

Re: [Rd] [R] S4 Methods with large numbers of args using memory

[This is probably more appropriate for R-devel so I'm responding there] Joseph Wang <[EMAIL PROTECTED]> writes: > Thanks all to the people on the r-help list for the backtick help. > > I've run into another problem. With my SWIG C++ wrapper for R, I'm finding > that S4 generic functions with la

[Rd] install.packages() does not warn when 'lib' arg is missing on Linux or Windows

Hello, Man page for 'install.packages' says that if the 'lib' arg is missing, then it "defaults to '.libPaths()[1]' with a warning". But, given the 'install.packages' source code, it seems that this warning is issued only when 'length(.libPaths()) > 1'. So typically, this warning will appear on Ma

Re: [Rd] install.packages() does not warn when 'lib' arg is missing on Linux or Windows

On Thu, 8 Jun 2006, Herve Pages wrote: > Hello, > > Man page for 'install.packages' says that if the 'lib' arg is missing, > then it "defaults to '.libPaths()[1]' with a warning". > But, given the 'install.packages' source code, it seems that this warning > is issued only when 'length(.libPaths())

[Rd] install.packages("C", dep=TRUE) does not always install indirect dependencies

Hello again, I've found another issue with 'install.packages'. 'install.packages("C", dep=TRUE)' will "fail" when the 2 following conditions are satisfied: - Package C depends on B which in turns depends on A but the Depends field in C doesn't list A. - Package B is already installed but n

Re: [Rd] install.packages() does not warn when 'lib' arg is missing on Linux or Windows

Prof Brian Ripley wrote: > On Thu, 8 Jun 2006, Herve Pages wrote: > >> Man page for 'install.packages' says that if the 'lib' arg is missing, >> then it "defaults to '.libPaths()[1]' with a warning". >> But, given the 'install.packages' source code, it seems that this >> warning >> is issued only

Re: [Rd] install.packages("C", dep=TRUE) does not always install indirect dependencies

On 6/8/2006 3:31 PM, Herve Pages wrote: > Hello again, > > I've found another issue with 'install.packages'. > 'install.packages("C", dep=TRUE)' will "fail" when the 2 following > conditions are satisfied: > - Package C depends on B which in turns depends on A but > the Depends field in C do

[Rd] NAs in unsplit factor

R-devel, Below is a simple example calling split and unsplit on a numeric vector of length 2 where 'f' is c(1,NA). > unsplit(split(c(1,2), c(1,NA)), c(1,NA)) [1] 1 0 I noticed that the call to vector in unsplit gives us 0 as the 2nd element of the result. Is this the intended result, as opposed

Re: [Rd] install.packages() does not warn when 'lib' arg is missing on Linux or Windows

Herve, On Jun 8, 2006, at 9:08 PM, Herve Pages wrote: > Man page for 'install.packages' says that if the 'lib' arg is missing, > then it "defaults to '.libPaths()[1]' with a warning". Where are you quoting from? I read (R 2.3.1): install.packages can be used to install new packages/bundles. It

Re: [Rd] NAs in unsplit factor

[Jeff Enos] >Below is a simple example calling split and unsplit on a numeric >vector of length 2 where 'f' is c(1,NA). >> unsplit(split(c(1,2), c(1,NA)), c(1,NA)) >[1] 1 0 >I noticed that the call to vector in unsplit gives us 0 as the 2nd >element of the result. >Is this the intended result,

Re: [Rd] install.packages("C", dep=TRUE) does not always install indirect dependencies

Duncan Murdoch <[EMAIL PROTECTED]> writes: >> conditions are satisfied: >> - Package C depends on B which in turns depends on A but >> the Depends field in C doesn't list A. >> - Package B is already installed but not package A (e.g. >> the user did 'install.packages("B", dep=FALSE)').