octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #49794] display vs. disp functions


From: Rik
Subject: [Octave-bug-tracker] [bug #49794] display vs. disp functions
Date: Fri, 9 Dec 2016 20:15:32 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0

Follow-up Comment #9, bug #49794 (project octave):

Bringing over comments from Julien at bug #49753

The output from an object which does not define a display method is something,
rather than an error, in Matlab.


>> display (x)

x = 

        stk_dataframe object: 4-by-2


This matches Amro's observation in comment #6.

This is easy enough to achieve by removing the input validation on isobject. 
If I comment out those lines, and use the following blank classdef file
blah.m


classdef blah
endclassdef


then I get the following results


octave:2> x = blah()
x =

<object blah>

octave:3> display (x)
x =

<object blah>

octave:4> y.a = x
y =

  scalar structure containing the fields:

    a =

    <object blah>


octave:5> display (y.a)
<object blah>


Does that look right?


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49794>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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