(missed the list the first time)

Perhaps an importHiddenFrom directive should be added to the namespace
vocabulary which can import a non-exported function. The non-exported
functions clearly exist somewhere, as package code can use them, so it
would not be impossible to allow that (though I'm not saying it would be
easy, as I haven't looked at how the namespace stuff is implemented).


On Thu, Aug 22, 2013 at 5:19 PM, Gabor Grothendieck <ggrothendieck@gmail.com
> wrote:

> On Thu, Aug 22, 2013 at 7:57 PM, Gabriel Becker <gmbecker@ucdavis.edu>
> wrote:
> > My understanding is that lookup happens in the imports before moving on
> to
> > the search path,  so if I understand you correctly I don't think that is
> an
> > issue. If A also *exported* f, that would be a problem...
> >
>
> A can only import f from B if f has been exported from B so while its
> not a problem for A, whenever anyone issues a library(B) f will be
> visible on the
> search path -- the problem of potential conflicts with f remains.
>
> B really only exported f so that A could import it but a side effect
> of that is that
> anyone who puts B on the search path makes f visible.
>



-- 
Gabriel Becker
Graduate Student
Statistics Department
University of California, Davis

	[[alternative HTML version deleted]]

