@@ -35,24 +35,29 @@ to the [ChangeLog](https://github.com/RcppCore/Rcpp/blob/master/ChangeLog) and
35
35
[ NEWS] ( https://github.com/RcppCore/Rcpp/blob/master/inst/NEWS.Rd ) are also
36
36
appreciated.
37
37
38
- Please note that C++ code in Rcpp must adhere to the C++98 standard. C++11 (and
39
- above) extensions are allowed, but must be appropriately guarded so that such
40
- code still successfully compiles under the C++98 standard.
38
+ Please note that C++ code in Rcpp must adhere to the prvailing C++ standards
39
+ as selected by the current R version ("R-release") and the upcoming R version
40
+ ("R-devel"). These days, _ Modern C++_ is well supported provided recent
41
+ compilers are used. As of 2024, R has supported C++17 for the past two
42
+ release cycles. We tend to be a little more conservative with Rcpp and still
43
+ support C++98 / C++11 as we know some users may be confronted with ancient
44
+ compilers.
41
45
42
46
### Coding Style
43
47
44
48
It would be nice if the contributed code followed existing conventions for
45
49
whitespace and indentation. We mostly follow the R Core style for with four
46
- spaces, and curlies where K&R would put them.
50
+ spaces, and curlies where K&R would put them. Our
51
+ [ editorconfig] ( https://editorconfig.org/ ) [ configuration
52
+ file] ( https://github.com/RcppCore/Rcpp/blob/master/.editorconfig ) selects
53
+ reasonable defaults.
47
54
48
55
### Asking Questions
49
56
50
57
Please direct general questions to the
51
58
[ Rcpp-devel] ( http://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel )
52
- mailing list (preferred, note that only subscribers can post), or alternatively
53
- post a question on
54
- [ Stack Overflow] ( http://stackoverflow.com/questions/tagged/rcpp ) using the
55
- ` [Rcpp] ` tag.
59
+ mailing list (preferred, note that only subscribers can post), or post an
60
+ issue at GitHub.
56
61
57
62
Are you a new user of Rcpp? You might find the
58
63
[ vignettes] ( https://cran.r-project.org/package=Rcpp ) helpful in getting
0 commit comments