Hello,
I've now moved all occurences of long long to a single file :
Rcpp/longlong.h
Currently this file is included by RcppCommon.h, but we could e.g.
decide not to include it by default so that client code that wants to
use long long could just do:
#include
#include
So that there are
Le 19/09/13 20:53, Dirk Eddelbuettel a écrit :
On 19 September 2013 at 20:08, Romain Francois wrote:
| Alright, so with these settings -pedantic turns on -Wlong-long
|
| I can disable them with -Wno-long-long
|
| Can we detect gcc with a configure and set -Wno-long-long, is that allowed ?
|
| Wh
On 19 September 2013 at 21:20, Romain Francois wrote:
| Le 19/09/13 20:53, Dirk Eddelbuettel a écrit :
| > People who really need long long already have an easy hook: -std=c++11
|
| Which does not work for me.
I don't follow. What does not work? Your compiler does not support it? You
have no ~/
On 19 September 2013 at 20:08, Romain Francois wrote:
| Alright, so with these settings -pedantic turns on -Wlong-long
|
| I can disable them with -Wno-long-long
|
| Can we detect gcc with a configure and set -Wno-long-long, is that allowed ?
|
| Where in the CRAN policies does it say that -ped
Alright, so with these settings -pedantic turns on -Wlong-long
I can disable them with -Wno-long-long
Can we detect gcc with a configure and set -Wno-long-long, is that allowed ?
Where in the CRAN policies does it say that -pedantic should be used ? I
did not find it.
We don't actually "co
What's in your Makevars.
I'm not able to reproduce this on __your__ machine with whatever are the
defaults.
Romain
Le 19/09/13 18:32, Dirk Eddelbuettel a écrit :
Darn. Romain's change look promising, but it seems that even with R-release I
get a bunch of warnings which would prevent this fr
On 19 September 2013 at 19:01, Romain Francois wrote:
| What's in your Makevars.
Try this
$ cat ~edd/.R/Makevars
and or cust do
$ test -d ~/.R || mkdir ~/.R
$ cp -vax ~edd/.R/Makevars ~/.R
| I'm not able to reproduce this on __your__ machine with whatever are the
| defaults.
"Defa
On 19 September 2013 at 17:54, Romain Francois wrote:
| > That's novel and could work. May need testing. May also need to be checked
| > against just using -std=c++11 / -std=c++0x which give us long long
rightaway.
|
| That just works. This is just a typedef.
Nope. See my follow-up.
| > Als
Darn. Romain's change look promising, but it seems that even with R-release I
get a bunch of warnings which would prevent this from going to CRAN. Maybe
the status quo wasn't so bad after all.
Current SVN head as below. Ubuntu 13.03, 64bit. G++ 4.7.3 selected via CXX in
the file ~/.R/Makevars
D
Le 19/09/13 17:39, Dirk Eddelbuettel a écrit :
On 19 September 2013 at 15:48, Romain Francois wrote:
| What I want is to change this:
|
| #if defined(__GNUC__)
| #if defined(__GXX_EXPERIMENTAL_CXX0X__) || (defined (__clang__) &&
| defined(__LP64__))
| #ifdef __LONG_LONG_MAX__
| __extension_
On 19 September 2013 at 15:48, Romain Francois wrote:
| What I want is to change this:
|
| #if defined(__GNUC__)
| #if defined(__GXX_EXPERIMENTAL_CXX0X__) || (defined (__clang__) &&
| defined(__LP64__))
| #ifdef __LONG_LONG_MAX__
| __extension__ typedef long long int rcpp_long_long_type;
|
I've put it in with some text explaining it.
// long long and unssigned long long support.
//
// given the current restriction of what might go to CRAN
// we can only use long long if we are running a gcc compatible (e.g. clang)
// compiler and the type is actually available (hence the test for
Le 19/09/13 15:30, Dirk Eddelbuettel a écrit :
On 19 September 2013 at 14:18, Romain Francois wrote:
| (rebrand as a Rcpp-devel question)
I just re-explained it on our internal rcpp-core list. The same points were
all made here too circa 2010 and are in the list archives.
Sure. You explained
On 19 September 2013 at 14:18, Romain Francois wrote:
| (rebrand as a Rcpp-devel question)
I just re-explained it on our internal rcpp-core list. The same points were
all made here too circa 2010 and are in the list archives.
In short, we are up against a CRAN Policy which wants
i) "standar
(rebrand as a Rcpp-devel question)
Le 19/09/13 13:58, Romain Francois a écrit :
Hello,
I'm trying to understand these:
#ifdef __GNUC__
#if defined(__GXX_EXPERIMENTAL_CXX0X__) || (defined (__clang__) &&
defined(__LP64__))
#ifdef __LONG_LONG_MAX__
__extension__ typedef long long int rcpp_lo
15 matches
Mail list logo
