Re: package autoload

[Ben Abbott]

> On Apr 15, 2016, at 07:42, LachlanA <address@hidden> wrote:
> 
> bpabbott wrote
>>> On Apr 15, 2016, at 07:47, Juan Pablo Carbajal &lt;
> 
>> ajuanpi+dev@
> 
>> &gt; wrote:
>>> 
>>> Toolboxes in matlab do not autoload
>> 
>> I've been using Matlab since 1990. I don't use many toolboxes, but none of
>> the toolboxes I have used require loading (optimization, for example).
>> 
>> Afaik, loading a toolbox is as simple as placing it in the path.
>> 
>> Ben
> 
> I think you are correct, Ben.  However, from what I gather, "loading" an
> Octave package is also simply adding it to the path.  Carnë explained on
> Tracker that we don't always want all the installed packages in the path
> because some conflict with each other, and some overload built-in functions.
> 
> My personal belief is that the __unimplemented__ function, which currently
> tells us which package we should load, should just load the package and
> continue (unless the same function is implemented in multiple packages, in
> which case it should list all of those packages and give an error).
> 
> That would most closely emulate the Matlab experience, while avoiding the
> problems Carnë described.

I often have trouble with m-file name conflicts between packages and/or core. 
Thus I prefer loading, and lean away from auto loading.

In any event, I only replied to clarify Matlab behavior.

Ben