Re: [Rd] RFC: API design of package "modules"

2014-04-29 Thread Gabriel Becker
On Tue, Apr 29, 2014 at 12:51 PM, Jeroen Ooms wrote: > On Tue, Apr 29, 2014 at 6:37 AM, Gabriel Becker > wrote: > > > > pkg::fun() will call function fun from the namespace of package pkg > > *without loading it onto the search path* > > It is important to use conventional terminology here. The

Re: [Rd] RFC: API design of package "modules"

2014-04-29 Thread Jeroen Ooms
On Tue, Apr 29, 2014 at 6:37 AM, Gabriel Becker wrote: > > pkg::fun() will call function fun from the namespace of package pkg > *without loading it onto the search path* It is important to use conventional terminology here. The package (and its dependencies) gets loaded but not *attached*. The `

Re: [Rd] RFC: API design of package "modules"

2014-04-29 Thread Gabriel Becker
Just a quick note because (perhaps embarassingly) I didn't know this for a long time: pkg::fun() will call function fun from the namespace of package pkg *without loading it onto the search path* > fastdigest::fastdigest("hi there") [1] "6fed537931bd23b42d3046c4d80790a1" > search() [1] ".GlobalEn

Re: [Rd] RFC: API design of package "modules"

2014-04-29 Thread Barry Rowlingson
On Mon, Apr 28, 2014 at 2:55 PM, Konrad Rudolph < konrad.rudolph+r-de...@gmail.com> wrote: > > So this is my question: what do other people think? Which is the most > useful and least confusing alternative from the users’ perspective? > The most useful is alternative is "write packages". The

[Rd] RFC: API design of package "modules"

2014-04-28 Thread Konrad Rudolph
Some time ago I’ve published the first draft of the package “modules” [1] which aims to provide a module system as an alternative to packages for R. Very briefly, this is aimed to complement the existing package system for very small code units which do not require the (small, but existing) overhea