[Octave-bug-tracker] [bug #58580] Changes to classdef files and additions to +package folders aren't reflected without magic incantations

[Kai Torben Ohlhus]

Update of bug #58580 (project octave):

                Severity:              3 - Normal => 1 - Wish               
                Priority:              5 - Normal => 1 - Later              
                  Status:                    None => Postponed              
                 Release:                   5.2.0 => dev                    
        Operating System:       Microsoft Windows => Any                    

    _______________________________________________________

Follow-up Comment #1:

Thank you for your bug report.  Please note, that Octave developers have only
limited resources to work on such a huge feature, such as introducing
object-orientated programming (OOP).

That things are not working 1:1 as in Matlab is documented in the manual.

> Since version 4.0, Octave has limited support for classdef classes. [...] 
An overview of what is missing can be found at
https://wiki.octave.org/Classdef.

https://octave.org/doc/v5.2.0/classdef-Classes.html

A few rule of thumb I figured out when working with classdef myself:

- use basic classdef OOP features
- use https://www.octave.org/doc/v5.2.0/XREFkeyboard.html for debugging
- use `clear classes` https://www.octave.org/doc/v5.2.0/XREFclear.html a few
times.  After breaking code changes, restart your Octave session.


    _______________________________________________________

Reply to this item at:

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

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