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

[Carnë Draug]

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

Can we rethink removal of this functions?

1. Alternative functions are meant to exist in 4.2 but deprecating them now
means that in version 3.8 and 4.0, there is no alternative to a user (the user
that writes code for others, not the end user). Yes, we can use ___java_get___
but that is not any different that using 'warning off; ___java_get___ ();
warning on;`. The whole point of deprecating functions, is to give users time
to adapt their code. This does not give them anytime. When the dot notation
will be available, is when this functions disappear.

2. Having a function for this things is handy. Should we really only support
dot notation? Why can't we have functions too? We have to create array,
objects, and to call methods. Why not to access and set field values? If so, I
guess that javaSet and javaGet may fit better next to JavaArray, javaMethod,
and javaObject.

3. Finally, the idea is that in 4.2 this notation will appear because classdef
will exist. But will it really? classdef is still in development but is it
really part of the plan to also make this notation work in 4.2? Even if it is
planned, it's doesn't sound safe to start the removal of these when we don't
really have the replacement working yet.

    _______________________________________________________

Reply to this item at:

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

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