search for: barthelm

...in its namespace, which quietly supersedes the default one. In my case it led to a bug that was rather hard to track down because it looked like non-deterministic behaviour. Shouldn't there at least be a warning about such side effects, the way library() tells you about masking? Best Simon Barthelme

...ntly loads the namespace if needed, and that "things may behave differently" after the use '::', because loading a namespace does have an effect on the R session ..., (and I still think `::` is much "over used") Martin >> On 1 sept. 2017, at 12:57, Simon Barthelm? <simon.barthelme at gipsa-lab.fr> wrote: >> >> Dear list >> >> I'm not sure whether this is a bug or an unavoidable consequence of the way packages are loaded, but there can be surprising side effects of calling a function via package::function....

...od unless it owns either the generic or the class. Here `formula.tools` owns neither. Instead of registering the method, it should export it like a regular function. This way S3 dispatch is based on lexical scoping rather than session-wide side effect. Lionel > On 1 sept. 2017, at 12:57, Simon Barthelm? <simon.barthelme at gipsa-lab.fr> wrote: > > Dear list > > I'm not sure whether this is a bug or an unavoidable consequence of the way packages are loaded, but there can be surprising side effects of calling a function via package::function. Here's an example using the...

...and that "things may behave differently" after the use '::', because > loading a namespace does have an effect on the R session ..., > (and I still think `::` is much "over used") > > Martin > > > >>> On 1 sept. 2017, at 12:57, Simon Barthelm? <simon.barthelme at gipsa-lab.fr> wrote: >>> >>> Dear list >>> >>> I'm not sure whether this is a bug or an unavoidable consequence of the way packages are loaded, but there can be surprising side effects of calling a function via package::function....