[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: |
Wed, 8 Feb 2017 12:35:01 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #29, bug #49794 (project octave):
The extra second input for display() should definitely be documented.
Since you are overloading the existing display() function in a new class, it
seems like it must have the same function signature as the function it
overrides. In this case, the function accepts two inputs so InputParser's
version of display should also accept two inputs. It doesn't have to do
anything with the second input if it doesn't want to. The choice of what to
implement is left to the programer.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49794>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/