Re: [Rd] syntax difference clusterExport in parallel and snow

2016-12-16 Thread Hervé Pagès
On 12/13/2016 09:33 AM, Prof Brian Ripley wrote: On 13/12/2016 17:05, Paul Johnson wrote: We got some errors and eventually figured out that parallel::clusterExport second argument is "varlist" while in snow::clusterExport it is "list". The user had loaded parallel first, but did something else

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Gábor Csárdi
I think that this problem is actually more general than just ABI versioning. The common definition of ABI refers to compiled code, but with R packages similar problems might happen (and they to happen) without any compiled code. I think the key issue is the concept of build-time dependencies. Whil

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Duncan Murdoch
On 16/12/2016 12:35 PM, Karl Millar wrote: A couple of points: - rebuilding dependent packages is needed if there is an ABI change, not just an API change. For packages like Rcpp which export inline functions or macros that might have changed, this is potentially any change to existing functio

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Karl Millar via R-devel
A couple of points: - rebuilding dependent packages is needed if there is an ABI change, not just an API change. For packages like Rcpp which export inline functions or macros that might have changed, this is potentially any change to existing functions, but for packages like Matrix, it isn't re

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Kirill Müller
Thanks for discussing this. On 16.12.2016 17:19, Dirk Eddelbuettel wrote: On 16 December 2016 at 11:00, Duncan Murdoch wrote: | On 16/12/2016 10:40 AM, Dirk Eddelbuettel wrote: | > On 16 December 2016 at 10:14, Duncan Murdoch wrote: | > | On 16/12/2016 8:37 AM, Dirk Eddelbuettel wrote: | > | > |

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Dirk Eddelbuettel
On 16 December 2016 at 11:00, Duncan Murdoch wrote: | On 16/12/2016 10:40 AM, Dirk Eddelbuettel wrote: | > On 16 December 2016 at 10:14, Duncan Murdoch wrote: | > | On 16/12/2016 8:37 AM, Dirk Eddelbuettel wrote: | > | > | > | > On 16 December 2016 at 08:20, Duncan Murdoch wrote: | > | > | Perhaps

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Duncan Murdoch
On 16/12/2016 10:40 AM, Dirk Eddelbuettel wrote: On 16 December 2016 at 10:14, Duncan Murdoch wrote: | On 16/12/2016 8:37 AM, Dirk Eddelbuettel wrote: | > | > On 16 December 2016 at 08:20, Duncan Murdoch wrote: | > | Perhaps the solution is to recommend that packages which export their | > | C-le

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Dirk Eddelbuettel
On 16 December 2016 at 10:14, Duncan Murdoch wrote: | On 16/12/2016 8:37 AM, Dirk Eddelbuettel wrote: | > | > On 16 December 2016 at 08:20, Duncan Murdoch wrote: | > | Perhaps the solution is to recommend that packages which export their | > | C-level entry points either guarantee them not to chan

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Duncan Murdoch
On 16/12/2016 8:37 AM, Dirk Eddelbuettel wrote: On 16 December 2016 at 08:20, Duncan Murdoch wrote: | Perhaps the solution is to recommend that packages which export their | C-level entry points either guarantee them not to change or offer | (require?) version checks by user code. So dplyr shou

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Dirk Eddelbuettel
On 16 December 2016 at 08:20, Duncan Murdoch wrote: | Perhaps the solution is to recommend that packages which export their | C-level entry points either guarantee them not to change or offer | (require?) version checks by user code. So dplyr should start out by | saying "I'm using Rcpp interf

Re: [Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Duncan Murdoch
I think there's one typo in your post which may confuse some readers; I've edited it inline below. My comments on the suggestion are at the bottom of the message. On 16/12/2016 5:35 AM, Kirill Müller wrote: Hi I'd like to suggest to make R more informative when a user updates a package A w

Re: [Rd] print.POSIXct doesn't seem to use tz argument, as per its example

2016-12-16 Thread Dirk Eddelbuettel
On 16 December 2016 at 10:19, Martin Maechler wrote: | > Jennifer Lyon | > on Thu, 15 Dec 2016 09:33:30 -0700 writes: | | > On the documentation page for DateTimeClasses, in the Examples section, | > there are the following two lines: | > | > format(.leap.seconds) # the leap

[Rd] Upgrading a package to which other packages are LinkingTo

2016-12-16 Thread Kirill Müller
Hi I'd like to suggest to make R more informative when a user updates a package A where there's at least one package B that has "LinkingTo: A" in its description. To illustrate the problem, assume package A is updated so that its C/C++ header interface (in inst/include) is changed. For pack

Re: [Rd] print.POSIXct doesn't seem to use tz argument, as per its example

2016-12-16 Thread Martin Maechler
> Jennifer Lyon > on Thu, 15 Dec 2016 09:33:30 -0700 writes: > On the documentation page for DateTimeClasses, in the Examples section, > there are the following two lines: > > format(.leap.seconds) # the leap seconds in your time zone > print(.leap.seconds, tz = "PST8PDT") #