[Octave-bug-tracker] [bug #55767] classdef property should not be the same as classdef name (at least for Matlab compatibility)

[John W. Eaton]

Follow-up Comment #1, bug #55767 (project octave):

I don't know why it would cause trouble.  Even something like the following
seems like it should work.


classdef foobar
  properties
    foobar;
  end
  methods
    function obj = foobar (...)
      obj.foobar = ...;
    end
  end
end


Inside methods, isn't it required to use obj.property to access properties? 
If so, then I don't see a conflict between property names and the constructor
(class) name.  It seems to me that you could even have a method that called
the constructor to create another object of the same type without having a
conflict.

Am I missing something?


    _______________________________________________________

Reply to this item at:

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

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