From murdoch@dunc@n @end|ng |rom gm@||@com  Sun Jun  7 00:05:40 2020
From: murdoch@dunc@n @end|ng |rom gm@||@com (Duncan Murdoch)
Date: Sat, 6 Jun 2020 18:05:40 -0400
Subject: [Rd] 
 Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
In-Reply-To: <24283.63773.386547.279873@rob.eddelbuettel.com>
References: <24283.59677.373606.9673@rob.eddelbuettel.com>
 <656c2251-4a91-47d5-c62e-848535dd744b@gmail.com>
 <2f768fa0-512c-2cbb-7bd2-30dda5b08b39@gmail.com>
 <24283.63773.386547.279873@rob.eddelbuettel.com>
Message-ID: <0e39d97a-e236-e7c4-c28c-4da295f9faf9@gmail.com>

On 06/06/2020 4:14 p.m., Dirk Eddelbuettel wrote:
> 
> On 6 June 2020 at 15:53, Duncan Murdoch wrote:
> | This change happened in August, 2019, about 10 months ago.  Perhaps this
> | message asking people to test R-devel is relevant:
> |
> | https://stat.ethz.ch/pipermail/r-devel/2020-May/079484.html
> 
> Touche :) And fully agree. Rcpp's unit tests covered Rcpp.package.skeleton()
> since about 2013. I have been keeping a local 'RD' build of R-devel in
> /usr/local/ for much longer to test both r-release and r-devel.  But test
> coverage is never full or complete, and what bit me here during a live demo
> (now at [1]) was the equivalent functionality tickled with from RStudio with
> similar-but-not-identical code.
> 
> And that part is certainly NOT contained in the unit tests. Can't win'em
> all. Still my bad for not checking NEWS, and bad luck this change did not get
> tickled by the many Rcpp tests runs here since the change was made.

The trouble with tests is that they make you think you've tested the 
code, and we all know that's impossible.

Duncan



[Rd] Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
Duncan Murdoch