Re: [Rd] Dialect for shell scripts

Hi all, Thanks to all for your responses. As pointed out by a few of you, using expr is indeed safer, and is what we ended up using in our script to get it accepted in CRAN. On 19/12/17 07:26, peter dalgaard wrote: (I suspect that the text in WRE is actually older than the current POSIX sta

Re: [Rd] Dialect for shell scripts

Solaris is pretty much dead at this point (closed source or not), but it is not the only oddball OS around. The need to support a wide palette of (Unix) OS variations has been rapidly declining in later years. Fifteen years ago every supercomputer seemed to have its own set of OS quirks and we

Re: [Rd] Dialect for shell scripts

I do not have a dog in this fight, but I have to ask: How much person time is worthwhile to invest in supporting Solaris 10? It has been closed-source (Post-Oracle)

Re: [Rd] Collaborative Wiki for fostering Open Innovation in R

I have found Apache JSPWiki solution, which might work and is open source: https://jspwiki.apache.org In addition, I will test xwiki, and give my insights about the tool on r-devel, as it might just be a resolutive tool for collaboration thanks to it's extensible architecture. Kind regards, Juan

[Rd] Fixed BLAS tests for external BLAS library

We build R with dynamically linked BLAS and LAPACK libraries, in order to use the AMD Core Math Library (ACML) multi-threaded implementation of these routines on our 64 core servers. This is great, and our users really appreciate it. However, when building like this, make check fails on the reg-B

Re: [Rd] Region subtag in package 'Language' field

> Jeroen Ooms writes: All standard (not private use or grandfathered) IETF language tags should be fine. What WRE says about ISO-639 codes is meant to explain the language subtags. Hth -k > I am looking for the appropriate field to let package authors to > declare the pkg documentation lang

Re: [Rd] Dialect for shell scripts

> Iñaki Úcar writes: Same from here: in addition to what the standards say, it always pays to be defensive and check "Portable Shell Programming" in the Autoconf manual. Among other things, this says '$((EXPRESSION))' Arithmetic expansion is not portable as some shells (most notably

Re: [Rd] Rcpp - Linking to DLL from another package?

On 18 December 2017 at 16:10, Jeroen Ooms wrote: | On Mon, Dec 18, 2017 at 2:40 PM, Dirk Eddelbuettel wrote: | > | > (Moderately wrong list: r-package-devel for packaging questions, rcpp-devel | > for Rcpp questions) | > | > On 18 December 2017 at 13:24, Stravs, Michael wrote: | > | I am trying t

Re: [Rd] Rcpp - Linking to DLL from another package?

On Mon, Dec 18, 2017 at 2:40 PM, Dirk Eddelbuettel wrote: > > (Moderately wrong list: r-package-devel for packaging questions, rcpp-devel > for Rcpp questions) > > On 18 December 2017 at 13:24, Stravs, Michael wrote: > | I am trying to make a package B that extends another package A. Package A >

Re: [Rd] Rcpp - Linking to DLL from another package?

(Moderately wrong list: r-package-devel for packaging questions, rcpp-devel for Rcpp questions) On 18 December 2017 at 13:24, Stravs, Michael wrote: | I am trying to make a package B that extends another package A. Package A uses Rcpp, and I want to extend a class X used there. It doesn't reall

[Rd] Rcpp - Linking to DLL from another package?

Hi, I am trying to make a package B that extends another package A. Package A uses Rcpp, and I want to extend a class X used there. So package A has src/X.h and inst/include/X.h class X { ... } src/X.cpp X::X( arguments ) { ... } My package B wants to do this: DESCRIPTION [...] LinkingTo: Rc

Re: [Rd] Dialect for shell scripts

For what it's worth, Autoconf does not assume that arithmetic expansion will be available. Instead, it emits the following shell code: if ( eval 'test $(( 1 + 1 )) = 2' ) 2>/dev/null; then eval 'func_arith () { func_arith_result=$(( $* )) }' else func_arith () { func_arith_result