Re: [Rcpp-devel] Testing for existence of named components

2012-03-29 Thread Patrick Burns
______ | Rcpp-devel mailing list | Rcpp-devel@lists.r-forge.r-project.org | https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel -- Patrick Burns patr...@burns-stat.com http://www.burns-stat.com http://www.portfolioprobe.com/blog twitter: @portfolioprobe ___ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel

Re: [Rcpp-devel] Datetime substraction bug ?

2013-04-02 Thread Patrick Burns
que support. | | ___ | Rcpp-devel mailing list | Rcpp-devel@lists.r-forge.r-project.org | https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel -- Patrick Burns patr...@burns-stat.com http:/

[Rcpp-devel] RInside under Windows

2012-02-14 Thread Patrick Burns
t_compatiblE' (with some chance of transcription errors) This is the same for both 32-bit and 64-bit. Suggestions? Pat -- Patrick Burns patr...@burns-stat.com http://www.burns-stat.com http://www.portfolioprobe.com/blog twitter: @portfolioprobe __

Re: [Rcpp-devel] RInside under Windows

2012-02-14 Thread Patrick Burns
because I get during the link ||=== pR1, Debug ===| obj\Debug\main.o:C:\pR1\Include\Rcpp\internal\wrap.h|348|undefined reference to `Rf_allocVector' . ||=== Build finished: 50 errors, 0 warnings ===| pascal Message d'origine ---- >De : "Patrick Burns" >À :

Re: [Rcpp-devel] RInside under Windows

2012-02-14 Thread Patrick Burns
;t start because R.dll is missing from your computer. Try reinstalling the program to fix this problem. This is using Rtools2.14 and R 2.14.1 with RInside_0.2.6 Rcpp_0.9.9 Pat On 14/02/2012 17:53, Dirk Eddelbuettel wrote: Hi Pat, On 14 February 2012 at 17:43, Patrick Burns wrote: | Good point abou

Re: [Rcpp-devel] RInside under Windows

2012-02-14 Thread Patrick Burns
On 14/02/2012 20:14, Dirk Eddelbuettel wrote: On 14 February 2012 at 20:04, Patrick Burns wrote: | Obviously I don't *really* know what I'm | doing, or even *sort of* know what I'm | doing. But that never stopped me before. | | Here is hopefully enough breadcrumbs to | help s

Re: [Rcpp-devel] RInside under Windows

2012-02-14 Thread Patrick Burns
On 14/02/2012 20:59, Dirk Eddelbuettel wrote: (resending with CC to list which I omitted a minute ago --Dirk) On 14 February 2012 at 20:47, Patrick Burns wrote: | | | On 14/02/2012 20:14, Dirk Eddelbuettel wrote: |> |> On 14 February 2012 at 20:04, Patrick Burns wrote: |> | Obviousl

Re: [Rcpp-devel] RInside under Windows

2012-02-14 Thread Patrick Burns
...@fiserv.com www.fiserv.com -Original Message- From: rcpp-devel-boun...@r-forge.wu-wien.ac.at [mailto:rcpp-devel-boun...@r-forge.wu-wien.ac.at] On Behalf Of Patrick Burns Sent: Tuesday, February 14, 2012 3:47 PM To: Dirk Eddelbuettel Cc: rcpp-de...@r-forge.wu-wien.ac.at Subject: Re: [Rcpp-devel]

Re: [Rcpp-devel] RInside under Windows

2012-02-15 Thread Patrick Burns
rror: unable to open the base package That seems like it might be a path problem as well but I'm not seeing how to fix it. Pat On 14/02/2012 21:52, Dirk Eddelbuettel wrote: On 14 February 2012 at 21:05, Patrick Burns wrote: | On 14/02/2012 20:59, Dirk Eddelbuettel wrote: |> |> (resendi

Re: [Rcpp-devel] RInside under Windows

2012-02-16 Thread Patrick Burns
a command window does not. Essentially R_LIBS_USER is okay in the double click route but the environment variable is necessary when run in a command window. Pat On 15/02/2012 14:03, Dirk Eddelbuettel wrote: On 15 February 2012 at 11:14, Patrick Burns wrote: | Dirk is once again correct. Th

Re: [Rcpp-devel] RInside under Windows

2012-02-16 Thread Patrick Burns
On 16/02/2012 13:38, Dirk Eddelbuettel wrote: On 16 February 2012 at 11:00, Patrick Burns wrote: | Success. Nice. | I'll tentatively offer this summary of the | important things to do. There are three | environment variables to set: I should document some of this. Maybe in Makefil

Re: [Rcpp-devel] RInside on windows

2012-02-19 Thread Patrick Burns
ient), and have received this message in error, any use, disclosure or distribution is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to the e-mail and permanently deleting the message from your computer and/or storage system. _