On Thu, Apr 23, 2009 at 1:02 PM, John W. Eaton
<address@hidden> wrote:
Doing that requires special knowledge about the way an octave_class
object is defined and breaks the model of having the object load
itself. At the point where enough information has been read from the
file to know that there is a problem, an octave_class object has
already been constructed, not an octave_map (struct) object. Yes, we
could have a special case for class objects, but I don't think that's
a good solution. We can probably do better than that, but as I said,
I think it will require some fairly substantial changes. Doing it
cleanly and consistently for all objects may require breaking backward
compatibility for objects defined in C++ classes. Not all of these
are part of Octave itself (for example, the fixed class in Octave
Forge).
jwe