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

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

[Octave-bug-tracker] [bug #60938] Classdef objects now referred to as "m


From: Rik
Subject: [Octave-bug-tracker] [bug #60938] Classdef objects now referred to as "m_object" by interpreter
Date: Sun, 18 Jul 2021 20:19:13 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.101 Safari/537.36

URL:
  <https://savannah.gnu.org/bugs/?60938>

                 Summary: Classdef objects now referred to as "m_object" by
interpreter
                 Project: GNU Octave
            Submitted by: rik5
            Submitted on: Sun 18 Jul 2021 05:19:11 PM PDT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: Confirmed
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Any

    _______________________________________________________

Details:

This is a regression from Octave 6.3.0.

See the attached clasdef code tstclass.m


classdef tstclass

  properties
    prop1
    prop2
    prop3
  endproperties

endclassdef


Now, create an object of this class:


octave:2> obj = tstclass
obj =

  tstclass m_object with properties:

      prop1: [0x0 double]
      prop2: [0x0 double]
      prop3: [0x0 double]



The interpreter should display


  tstclass object with properties:


At least, this is what it does for version 6.3.0.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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