Actually I have integrated more complex classes copying Romain's example.
This included polymorphism (see the answers and discussion around question with
subject "Module with vector of a class with inheritance, how to avoid slicing"
on this list). I failed to handle very well the case of a templ
On 13 May 2013 at 21:25, Robin Girard wrote:
|
http://romainfrancois.blog.free.fr/index.php?post/2012/10/25/Rcpp-modules-more-flexible
Oh a good one indeed -- I had forgotten about that aspect (and in fact not
used it yet in a project of mine).
This may indeed work for Anwar, so thanks for the
http://romainfrancois.blog.free.fr/index.php?post/2012/10/25/Rcpp-modules-more-flexible
sorry about that
R.
- Mail original -
De: "Dirk Eddelbuettel"
À: "Robin Girard"
Cc: "Anwar Ludin" ,
[email protected], "Dirk Eddelbuettel"
Envoyé: Lundi 13 Mai 2013 19:25:09
Obj
On 13 May 2013 at 19:05, Robin Girard wrote:
| As suggested in the example of Romain's Blog
| here http://romainfrancois.blog.free.fr/
There are dozens of posts regarding Rcpp on his blog. If you refer to one
such post, could you show us the relevant (and presumably still valid) URL?
Otherwi
As suggested in the example of Romain's Blog
here http://romainfrancois.blog.free.fr/
you need to define the class before "exposing" it and then implement it (I
think it is also important that using namespace Rcpp comes after the exposed
stuff).
class Foo ;
RCPP_EXPOSED_CLASS(Foo)
using name
On 13 May 2013 at 16:11, Anwar Ludin wrote:
| Hi Dirk,
|
| Thanks for your answer!
|
| So if I understand correctly, the fact that I exposed previously
| Portfolio is not enough?
What do you mean by "exposed"?
You defined it, so the compiler will no
comlain about 'unknown type'. But that
Hi Dirk,
Thanks for your answer!
So if I understand correctly, the fact that I exposed previously
Portfolio is not enough?
I still need to provide wrap the template specialization:
template <> SEXP wrap( const Portfolio& ) ;
Thanks,
Anwar
On 05/13/2013 03:28 PM, Dirk Eddelbuettel wrote
On 13 May 2013 at 14:59, Anwar Ludin wrote:
| Hello,
|
| I'm trying to expose 2 classes from a Rcpp module:
|
| class Portfolio{
| private:
| std::string portfolioId, description;
| public:
| Portfolio(std::string portfolioId, std::string description)
| : portfolioId(portfol
Hello,
I'm trying to expose 2 classes from a Rcpp module:
class Portfolio{
private:
std::string portfolioId, description;
public:
Portfolio(std::string portfolioId, std::string description)
: portfolioId(portfolioId), description(description) {}
std::string getPortfol
OK. No problem. Thanks for the fast response.
On Mon, May 13, 2013 at 2:51 PM, JJ Allaire wrote:
> No, there currently isn't a way to cause it look inside subfolders.
>
> J.J.
>
> On Mon, May 13, 2013 at 5:48 AM, Finlay Scott wrote:
>
>> Hi,
>> I am putting a package together using Rcpp attribu
No, there currently isn't a way to cause it look inside subfolders.
J.J.
On Mon, May 13, 2013 at 5:48 AM, Finlay Scott wrote:
> Hi,
> I am putting a package together using Rcpp attributes. It's all working
> well so far (thanks to help I previously I got from this list).
>
> To organise my sourc
Hi,
I am putting a package together using Rcpp attributes. It's all working
well so far (thanks to help I previously I got from this list).
To organise my source files a little better I wanted to have a subfolder in
the /src folder (not essential but makes things a little neater). The *.cpp
files
12 matches
Mail list logo
