[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51801] OO: constructor without arguments
|
From: |
Mike Miller |
|
Subject: |
[Octave-bug-tracker] [bug #51801] OO: constructor without arguments |
|
Date: |
Mon, 21 Aug 2017 15:59:32 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #1, bug #51801 (project octave):
Are you suggesting that the wording should be changed from "it should return a
valid object" to "it must return a valid object"?
I disagree with that, however this is only describing the situation for legacy
style classes. What we need is a rewrite of the OO section of the manual to
cover classdef classes, which do always return a valid object, because it's
not even left up to the user to assign a return value.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51801>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/