[Octave-bug-tracker] [bug #41239] Dot notation for accessing Java static class fields

[Carnë Draug]

Follow-up Comment #10, bug #41239 (project octave):

Rik said:
> All sensible reasons. I'm not opposed to keeping around some
> version of javaGet/javaSet until there is a guaranteed working
> replacement.

Then can we please "un"deprecate jave_get and java_set now? Because some
working does not exist yet. What will I do if I release a package 2 months
before 4.2?

> After dot notation is available it would be wise to bring this
> issue back to the Octave Maintainers list to see if we want to
> diverge from the Matlab Java interface or not. It would be a
> superset of Matlab, but it still might create problems if
> people code to the Octave interface, say while working at home,
> and then bring it to work to simulate on Matlab.

This already happens and is not a problem. We have rows, columns, ishandle,
iscolormap, prepad, postpad, etc... We have ! for negation, and # for
comments. Octave users know there's functionality in Octave that is still
missing in Matlab.

    _______________________________________________________

Reply to this item at:

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

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