Re: Octave class search path problem

[John W. Eaton]

On 26-Oct-2011, Carnë Draug wrote:

| 2011/10/26 John Evans <address@hidden>
| > Unfortunately, the actual code contains sensitive IP, however, I can post 
my contrived example. You can find the contents of /fooBar/@foo/foo.m as well 
as a small example of my problem at
| > http://pastebin.com/ZD4TjMEg
| 
| The problem is in your IP then. It should work if you change your
| object constructor to something like:
| 
| function x = foo()
|         x = struct;
|         x = class(x, "foo");
| endfunction

That the constructor doesn't create a proper class object is a
separate problem.  When searching for class constructors, Octave
doesn't look at the contents of the constructor function.  All it does
it search for a function file with the same name as a class directory
somewhere in the path.  There must have been a bug in 3.2.4 in the way
that was done, or in the way addpath modified the search path.

jwe