[Octave-bug-tracker] [bug #56385] operations don't compose

[anonymous]

Follow-up Comment #6, bug #56385 (project octave):

The same problem also happens for the method `horzcat`. This can be checked by
adding to the previously attached class the following method (inside
myFavoriteDouble.m)


    function result = horzcat(this, that)
        result = [double(this), double(that)];
    end


The following command then produces no output:


octave:1> [myFavDouble(1)+myFavDouble(2), myFavDouble(1)+myFavDouble(3)]


For more elaborated classes, it seems that this problem of failing to return
an object can cause a segmentation fault, leading octave to quit. Namely I
observed the following error:


warning: error caught while executing handle class delete method:
can't perform indexing operations for <unknown type> type
fatal: caught signal Segmentation fault -- stopping myself...
Segmentation fault


I could try to add another comment for every method I encounter which displays
this behavior, but that would certainly not be exhaustive. Maybe it would be
safer to test systematically every method that can be overloaded in a classdef
for stability under various compositions?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56385>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/