problems with "aoutoload" in 3.1.55

[Carlo de Falco]

On 22 May 2009, at 22:08, John W. Eaton wrote:

> On 22-May-2009, Carlo de Falco wrote:
>
> | If you decide to take this approach,  could you suggest a way to
> | modify my package so that the autoladed version is used by default  
> and
> | the m-file is only kept as a backup resource?
>
> Create a single .oct file for each function you wish to define instead
> of autoloading them from a single .oct file?

Yes, that's what I am usually doing. But in this case the functions in  
the .oct file depend on each other,
so I had to put them in the same file to avoid using to many calls to  
feval...

> jwe
c.