Re: Module take-over policy

2017-03-28 Thread Richard Hainsworth
True in theory: the meta data for different modules, such as version and auth, exist. In practice: so far as I know, (1) :auth is ignored, (2) the ecosystem has no 'top-level' mechanism Two situations: a) a new environment is being created, so all modules should be the most recent. Which

Re: Module take-over policy

2017-03-28 Thread Brad Gilbert
Responses inline On Tue, Mar 28, 2017 at 10:37 PM, Richard Hainsworth wrote: > I've seen a couple of references to modules that no longer work; it's > inevitable with a new language. > > There is a balance between having respect for / protecting the original > developer, and also keeping a useful