Rcpp uses __ as a prefix for identifiers in auto-generated code (e.g. here and here). This is problematic, since __ is not not valid in C++ identifiers (it’s reserved for use by the compiler).
Such identifiers are for instance used by standard library implementations. And although most modern implementations try to avoid aggravating users, and so use more explicit conventions in their macro names, a simple grep through the libc++ implementation shows a few macros with names such as __need_size_t (and more in libstdc++), so it’s not unthinkable that there might be conflicts with future versions of some compilers.
It would be better to replace these instances with a legal identifier token, e.g. Rcpp_.
Rcpp uses
__as a prefix for identifiers in auto-generated code (e.g. here and here). This is problematic, since__is not not valid in C++ identifiers (it’s reserved for use by the compiler).Such identifiers are for instance used by standard library implementations. And although most modern implementations try to avoid aggravating users, and so use more explicit conventions in their macro names, a simple grep through the libc++ implementation shows a few macros with names such as
__need_size_t(and more in libstdc++), so it’s not unthinkable that there might be conflicts with future versions of some compilers.It would be better to replace these instances with a legal identifier token, e.g.
Rcpp_.