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

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

[Octave-bug-tracker] [bug #54249] essential explanation on class and cla


From: anonymous
Subject: [Octave-bug-tracker] [bug #54249] essential explanation on class and classdef usage
Date: Thu, 5 Jul 2018 02:32:09 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0

URL:
  <http://savannah.gnu.org/bugs/?54249>

                 Summary: essential explanation on class and classdef usage
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Thu 05 Jul 2018 06:32:07 AM UTC
                Category: Documentation
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Documentation
                  Status: None
             Assigned to: None
         Originator Name: thomasp
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

In the documentation of the "class" and "classdef" keywords on the octave.org
website ([1], as of 2018-07-05), the following pretty essential information is
missing:

1. In section 34. or 34.1, there should be mention that a new class definition
syntax using "classdef" is existing which is more powerful than old-style
class definition.

2. In section 34.2, there should be mention (e.g. by example) that in
old-style class objects, methods must be accessed like "disp(obj,
further_args)". (for Matlb compatibility)

3. In the event of a change in the class code, apparently the internally
stored class definition needs to be updated manually by user. This clearly
must be mentioned (e.g. in 34.1 and 34.6?). Possibly, a warning should be
produced if a code change in the definition can be detected (e.g. on object
creation).

----------
[1] https://octave.org/doc/interpreter/
section 34.





    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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