Re: package manager patch + problem

[John W. Eaton]

On 28-Feb-2007, Paul Kienzle wrote:

| 
| On Feb 28, 2007, at 8:35 AM, David Bateman wrote:
| 
| > What about the solution in octave itself that uses
| >
| > autoload ("airy", fullfile (fileparts (mfilename ("fullpath")),
| > "besselj.oct"));
| >
| > in the PKG_ADD file in the directory with besselj.oct.
| > mfilename is run on the PKG_ADD file itself and there
| > is no concern that the path is not absolute..
| >
| > The disadvantage is that the PKG_ADD file must be in
| > the same directory as the file being autoloaded..

I think that is the expected location for a PKG_ADD file.

| The other disadvantage is that it is ugly.
| 
| The documentation for file_in_loadpath says it
| returns the absolute path, and testing on
| octave 2.1.69 OS X supports this.

I think that using file_in_loadpath can cause some confusion if there
are multiple functions with the same name in the loadpath.

jwe