octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: package manager patch + problem


From: John W. Eaton
Subject: Re: package manager patch + problem
Date: Fri, 2 Mar 2007 12:37:53 -0500

On  2-Mar-2007, David Bateman wrote:

| John W. Eaton wrote:
| > | 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
| >
| >   
| That might be addressed with something like
| 
| autoload("glog",file_in_loadpath("gf.oct")[1]);

I don't think this is valid syntax.  Maybe you meant something else?
But if it was

  file_in_loadpath ("gf.oct", "all"){1}

then I don't see the difference, as

  file_in_loadpath ("gf.oct")

should return the first entry anyway.

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]