Re: File extensions in __list_functions__

[Jaroslav Hajek]

On Tue, May 26, 2009 at 6:02 PM, John W. Eaton <address@hidden> wrote:
> On 26-May-2009, John W. Eaton wrote:
>
> | OK.  Currently, __list_functions__ (DIR) is just calling
> |
> |   string_vector fl = load_path::files (dir);
> |
> | so it gets a list of all files, not just .m, .oct, and .mex files.
> | Maybe we need a
> |
> |   load_path::fcn_names (DIR)
> |
> | function that returns the names of the functions defined in a
> | particular directory, regardless of whether DIR is actually in the
> | load path.  This function would just be in the load_path class becuase
> | it seems to be a related function.
> |
> | I'll add this function and fix __list_functions__ (DIR) unless you
> | object.
>
> Sorry, I misread what load_path::files is doing.  It is returning only
> function files.  So I added an optional argument to allow it to omit
> file extensions.  The change is checked in here:
>
>  http://hg.savannah.gnu.org/hgweb/octave/rev/95445f9f5976
>
> Should this go in 3.2.0?
>

I think so. I'll include this in RC4.


-- 
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz