search for: gipsa

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 formula.tools package: form <- a ~ b as.character(form) formula.tools::lhs(form) as.character(form) The first call to as.character returns: [1] "~"

...d, 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. Here's an example using th...

...ric 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 formula.tools package: > &...

...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. Here's an example using th...