[Octave-bug-tracker] [bug #51470] OF-windows: COM objects do not accept method arguments

[Philip Nienhuis]

Update of bug #51470 (project octave):

                  Status:          Ready For Test => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #13:

Sure, but does the builtin methods.m (in scripts/general/) still work for for
classdef & Java objects then? I suppose it'll get shadowed.

Since your fix in comment #4, methods.m in core now does at least something
for COM objects.
Looking in scripts/general/methods.m, for "general" objects __methods__ is
called (in ov-class.cc) that doesn't know about COM objects:

>> methods (app)
Methods for class octave_com_object:
delete   get      invoke   release  set


which are general COM methods (optionally with "com_" prefixed) while the real
list is shown (partly) in comment #9.

So I think when the windows package gets loaded it is __methods__() that needs
to be overloaded (as we can't add COM-specific stuff to core Octave).

That's as far as my probably oversimplified OOP reasoning goes :-)


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/