Re: [Rcpp-devel] Rcpp compiler support and tests for suitable compilers

Le 03/12/10 01:52, Dominick Samperi a écrit : On Tue, Nov 30, 2010 at 3:20 PM, Dirk Eddelbuettel mailto:e...@debian.org>> wrote: The Rcpp (and RInside) documentation attempts to make it clear that the set of supported compilers is definied by R Core via the support in R and its

Re: [Rcpp-devel] Rcpp compiler support and tests for suitable compilers

On Tue, Nov 30, 2010 at 3:20 PM, Dirk Eddelbuettel wrote: > > The Rcpp (and RInside) documentation attempts to make it clear that the set > of supported compilers is definied by R Core via the support in R and its > tools. > > Rcpp is first and foremost an extension package for R, it does not liv

Re: [Rcpp-devel] [Rd] Terminology clarification (Re: GPL and R Community Policies (Rcpp)

On Thu, Dec 2, 2010 at 6:43 PM, Joris Meys wrote: > On Fri, Dec 3, 2010 at 12:38 AM, Dominick Samperi > wrote: > > > We? Romain did not arrive on the scene until after November of 2009. > > > > To live outside the law you must be honest --- Bob Dylan. > > > >[[alternative HTML version de

Re: [Rcpp-devel] [Rd] Terminology clarification (Re: GPL and R Community Policies (Rcpp)

On Thu, Dec 2, 2010 at 5:58 PM, Dirk Eddelbuettel wrote: > > On 2 December 2010 at 17:23, Dominick Samperi wrote: > | OK, since you are so accomodating, then please remove all reference to > | my name from Rcpp as I do not want to be subject to arbitrary revisions > of > | my status. I may not ha

Re: [Rcpp-devel] idiom for determining the (S3) class of an R object?

Sorry, didn't see this before my last mail. Looks like a better solution. On 12/2/10 1:55 PM, Romain Francois wrote: Le 02/12/10 22:51, Romain Francois a écrit : Le 02/12/10 22:40, Douglas Bates a écrit : I currently use constructions like if (as(lst.attr("class")) != "family") throw std::ru

Re: [Rcpp-devel] idiom for determining the (S3) class of an R object?

There is a related routine in R_HOME/src/main/attrib.c: EXP R_data_class(SEXP obj, Rboolean singleString) { SEXP value, klass = getAttrib(obj, R_ClassSymbol); int n = length(klass); if(n == 1 || (n > 0 && !singleString)) return(klass); if(n == 0) { SEXP dim = getAttrib(obj

Re: [Rcpp-devel] [Rd] Terminology clarification (Re: GPL and R Community Policies (Rcpp)

On Thu, Dec 2, 2010 at 5:58 PM, Dirk Eddelbuettel wrote: > > On 2 December 2010 at 17:23, Dominick Samperi wrote: > | OK, since you are so accomodating, then please remove all reference to > | my name from Rcpp as I do not want to be subject to arbitrary revisions > of > | my status. I may not ha

Re: [Rcpp-devel] [Rd] Terminology clarification (Re: GPL and R Community Policies (Rcpp)

On 2 December 2010 at 17:23, Dominick Samperi wrote: | OK, since you are so accomodating, then please remove all reference to | my name from Rcpp as I do not want to be subject to arbitrary revisions of | my status. I may not have the right to say how my prior work will be used, | but I think I ha

Re: [Rcpp-devel] [Rd] Terminology clarification (Re: GPL and R Community Policies (Rcpp)

While we are on the subject of terminology, it is important to remember that Rcpp is a C++ library, and this is often confused with Rcpp the package. I changed the package name to limit confusion on this point, but the package name was changed back to Rcpp for the "fork" (or "branch", not sure what

Re: [Rcpp-devel] [Rd] Terminology clarification (Re: GPL and R Community Policies (Rcpp)

On Thu, Dec 2, 2010 at 4:35 PM, Dirk Eddelbuettel wrote: > > There are repeated claims concerning a "Rcpp fork". Let's address both > terms > in turn. > > i) Rcpp was used in November 2008 as the name for a re-launch of a package >which had seen releases on CRAN in 2005/2006 during which it

Re: [Rcpp-devel] idiom for creating an informative message for an exception

Le 02/12/10 22:53, Dirk Eddelbuettel a écrit : On 2 December 2010 at 22:46, Romain Francois wrote: | Le 02/12/10 22:15, Douglas Bates a écrit : |> In the lme4a package I mixed calls to Rf_error and throwing C++ |> exceptions. This is causing problems and I plan to replace the calls |> to Rf_

Re: [Rcpp-devel] idiom for determining the (S3) class of an R object?

Le 02/12/10 22:51, Romain Francois a écrit : Le 02/12/10 22:40, Douglas Bates a écrit : I currently use constructions like if (as(lst.attr("class")) != "family") throw std::runtime_error("glmFamily requires a list of (S3) class \"family\""); Is there a cleaner way that I haven't discovered yet

Re: [Rcpp-devel] idiom for creating an informative message for an exception

On 2 December 2010 at 22:46, Romain Francois wrote: | Le 02/12/10 22:15, Douglas Bates a écrit : | > In the lme4a package I mixed calls to Rf_error and throwing C++ | > exceptions. This is causing problems and I plan to replace the calls | > to Rf_error by exceptions so that there is a consistent

Re: [Rcpp-devel] idiom for determining the (S3) class of an R object?

On 2 December 2010 at 15:40, Douglas Bates wrote: | I currently use constructions like | | if (as(lst.attr("class")) != "family") | throw std::runtime_error("glmFamily requires a list of (S3) class | \"family\""); | | Is there a cleaner way that I haven't discovered yet. Seems c

Re: [Rcpp-devel] idiom for determining the (S3) class of an R object?

Le 02/12/10 22:40, Douglas Bates a écrit : I currently use constructions like if (as(lst.attr("class")) != "family") throw std::runtime_error("glmFamily requires a list of (S3) class \"family\""); Is there a cleaner way that I haven't discovered yet. This method is error-pr

Re: [Rcpp-devel] idiom for creating an informative message for an exception

Le 02/12/10 22:15, Douglas Bates a écrit : In the lme4a package I mixed calls to Rf_error and throwing C++ exceptions. This is causing problems and I plan to replace the calls to Rf_error by exceptions so that there is a consistent approach. Many of the calls to Rf_error take advantage of the f

Re: [Rcpp-devel] object '.pointer' not found

Le 02/12/10 22:27, Andrew Redd a écrit : I realized that one again I responded off list. But yes my problem was fixed. I found the hard way that classes now require explicit constructors. Thanks, Andrew I guess you mean that it is required to explicitely expose them ? That's true. This has in

[Rcpp-devel] idiom for determining the (S3) class of an R object?

I currently use constructions like if (as(lst.attr("class")) != "family") throw std::runtime_error("glmFamily requires a list of (S3) class \"family\""); Is there a cleaner way that I haven't discovered yet. This method is error-prone because the S3 class of an object is a Ch

[Rcpp-devel] Terminology clarification (Re: [Rd] GPL and R Community Policies (Rcpp)

There are repeated claims concerning a "Rcpp fork". Let's address both terms in turn. i) Rcpp was used in November 2008 as the name for a re-launch of a package which had seen releases on CRAN in 2005/2006 during which it was also renamed to RcppTemplate. Hence no package of name Rcpp h

Re: [Rcpp-devel] object '.pointer' not found

I realized that one again I responded off list. But yes my problem was fixed. I found the hard way that classes now require explicit constructors. Thanks, Andrew On Thu, Dec 2, 2010 at 1:42 PM, Romain Francois wrote: > Hmm. Actually my toy example was not right (it is getting late in france, I >

[Rcpp-devel] idiom for creating an informative message for an exception

In the lme4a package I mixed calls to Rf_error and throwing C++ exceptions. This is causing problems and I plan to replace the calls to Rf_error by exceptions so that there is a consistent approach. Many of the calls to Rf_error take advantage of the fact the Rf_error implicitly calls sprintf to

Re: [Rcpp-devel] object '.pointer' not found

Hmm. Actually my toy example was not right (it is getting late in france, I think I've had enough screen time for one day). This works for me : require(inline) require(Rcpp) fx <- cxxfunction(, "", includes = ' class Foo { public: Foo() : x(2.0){} Foo(double x_) : x(x_)

Re: [Rcpp-devel] object '.pointer' not found

Apparently, creation of the object works, but the show method for the class has a problem, so you should be able to do: obj <- new(Module("GPU_BAYES",'gpuBayes')$data3) Can you confirm ? (I only tried on a toy example) but then when you print the object, it bombs out. I'm narrowing this down,

Re: [Rcpp-devel] object '.pointer' not found

On Thu, Dec 2, 2010 at 2:47 PM, Romain Francois wrote: > Le 02/12/10 20:34, Dominick Samperi a écrit : > >> On Thu, Dec 2, 2010 at 2:31 PM, Andrew Redd > > wrote: >> >>That exposes the data3 class, but does not solve the pointer problem. >> >> >> Add a default contruct

Re: [Rcpp-devel] object '.pointer' not found

Le 02/12/10 20:34, Dominick Samperi a écrit : On Thu, Dec 2, 2010 at 2:31 PM, Andrew Redd mailto:amr...@gmail.com>> wrote: That exposes the data3 class, but does not solve the pointer problem. Add a default contructor. This would have been detected at compile time. Please read the vigne

Re: [Rcpp-devel] object '.pointer' not found

That's odd that it only happens for your package. Guess #2 is that it might be a namespace issue. Can you try adding: import(methods) import(Rcpp) to your NAMESPACE file Romain Le 02/12/10 20:31, Andrew Redd a écrit : That exposes the data3 class, but does not solve the pointer problem. On

Re: [Rcpp-devel] object '.pointer' not found

I have a default constructor. -Andrew On Thu, Dec 2, 2010 at 12:34 PM, Dominick Samperi wrote: > > > On Thu, Dec 2, 2010 at 2:31 PM, Andrew Redd wrote: > >> That exposes the data3 class, but does not solve the pointer problem. > > > Add a default contructor. > > >> >> >> On Thu, Dec 2, 2010 at 1

Re: [Rcpp-devel] object '.pointer' not found

On Thu, Dec 2, 2010 at 2:31 PM, Andrew Redd wrote: > That exposes the data3 class, but does not solve the pointer problem. Add a default contructor. > > > On Thu, Dec 2, 2010 at 12:24 PM, Romain Francois > wrote: > >> Le 02/12/10 20:05, Andrew Redd a écrit : >> >> I updated to the new Rcpp

Re: [Rcpp-devel] object '.pointer' not found

That exposes the data3 class, but does not solve the pointer problem. On Thu, Dec 2, 2010 at 12:24 PM, Romain Francois wrote: > Le 02/12/10 20:05, Andrew Redd a écrit : > > I updated to the new Rcpp 0.8.9 then added a new function to my class. >> It compiles fine the Module is found and loads t

Re: [Rcpp-devel] object '.pointer' not found

Le 02/12/10 20:05, Andrew Redd a écrit : I updated to the new Rcpp 0.8.9 then added a new function to my class. It compiles fine the Module is found and loads the class definition seems to be there, but when I try to create a instance of the class I get the error: R> new(Module("GPU_BAYES",'gp

[Rcpp-devel] object '.pointer' not found

I updated to the new Rcpp 0.8.9 then added a new function to my class. It compiles fine the Module is found and loads the class definition seems to be there, but when I try to create a instance of the class I get the error: R> new(Module("GPU_BAYES",'gpuBayes')$data3) Error in get(".pointer", env

Re: [Rcpp-devel] [Rd] GPL and R Community Policies (Rcpp)

Your original question is predicated on the notion that people are "disseminating misleading information about" you, with this phrase: "a small portion of the code is based on code written during 2005 and 2006 by Dominick Samperi". While it may be difficult to qualify contributions to a joint proj

Re: [Rcpp-devel] [Rd] GPL and R Community Policies (Rcpp)

On Thu, Dec 2, 2010 at 10:47 AM, Joris Meys wrote: > On Thu, Dec 2, 2010 at 4:31 PM, Dominick Samperi > wrote: > > > > Worst yet is having to compete with your own work. > > > About which competition are we talking then? I'm sorry, but the vast > majority of the 7 lines of code of the rcpp a

Re: [Rcpp-devel] [Rd] GPL and R Community Policies (Rcpp)

On Thu, Dec 2, 2010 at 10:21 AM, Spencer Graves < spencer.gra...@structuremonitoring.com> wrote: > On 12/2/2010 6:20 AM, Martyn Plummer wrote: > >> Dear Dominick, >> >> The R community does not have a conflict resolution mechanism. We are >> quite used to disputes that end with one party, usually

Re: [Rcpp-devel] [Rd] GPL and R Community Policies (Rcpp)

On Thu, Dec 2, 2010 at 9:20 AM, Martyn Plummer wrote: > Dear Dominick, > > The R community does not have a conflict resolution mechanism. We are > quite used to disputes that end with one party, usually a recognized > authority, saying "No, you are objectively, verifiably wrong". We > cannot,

Re: [Rcpp-devel] Rcpp-devel Digest, Vol 14, Issue 4

> This is not about this particular case, it is about "general ideas" > along the lines of your original post. As far as I can tell, this is clearly not the appropriate forum for "general ideas" about software. Nor is it appropriate to cross-posting material from other forums or personal emails t

Re: [Rcpp-devel] [Rd] GPL and R Community Policies (Rcpp)

On Thu, Dec 2, 2010 at 2:51 AM, Gavin Simpson wrote: > On Wed, 2010-12-01 at 20:24 -0500, Dominick Samperi wrote: > > > > Just to be clear I have never used the package and am not truly > > > commenting on this particular case but only the general ideas in this > > > thread. Also I was not sugge

Re: [Rcpp-devel] [Rd] GPL and R Community Policies (Rcpp)

On Thu, Dec 2, 2010 at 2:45 AM, Sean O'Riordain wrote: > Good morning Dominick, > > I don't use the Rcpp package and have only the vaguest notions of its > history. > > One of your requests is that your name might be removed from the project as > you no longer wish to be associated with it. Howe