On Mon, Nov 19, 2012 at 1:36 PM, Dirk Eddelbuettel <e...@debian.org> wrote:
>
> On 19 November 2012 at 19:18, Chris Jefferson wrote:
> | This is also fixed in svn (having just checked it out).
>
> Thanks for that!
>
> | You can locally fix it by changing line 36 from:
> |
> | conversion_to_bool_is_forbidden<x>{
> |
> | to:
> |
> | forbidden_conversion<x>{
>
>
> [...]
>
> | I would guess this is caused by clang 3.0's c++11 support not being very
> good.
> | I certainly would be tempted not to try to fix it, unless there is a good
> | reason for it. clang 3.2 should be out very shortly, with very good
> support.
>
> We have the added issue that we cannot upload code requiring C++11 to the R
> repo network -- it is deemed "not portable". For that reason, our code in
> Rcpp is not well tested for C++11, or at all for that matter.
>
> We put some hooks in two years ago and have been discouraged since. We are
> looking forward to using these features once C++11 becomes more widely
> available and CRAN allows it. For now, our hands are tied.
>
> So I had recommended earlier that Thell just drop this. I don;t think that
> it is a fruitful avenue right now. I am not happy about this but one can
> only fight so many battles at once.
>
> Dirk
>
> --
> Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com
>
The future happens regardless of anything else. c++11 will end up being
used and CRAN will have to follow or be replaced, or so history shows.
--
Sincerely,
Thell
_______________________________________________
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
