[Octave-bug-tracker] [bug #48866] __java_get/set__

[Ernst Reissner]

URL:
  <http://savannah.gnu.org/bugs/?48866>

                 Summary: __java_get/set__
                 Project: GNU Octave
            Submitted by: ernstreissner
            Submitted on: Tue 23 Aug 2016 09:33:54 AM GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

Strictly speaking, this is not a bug 
but an implementation which is too complicated 
and the result of an incomplete change: 

Whereas functions javaMethod and javaObject 
turned from definitions via m-file, 
java_get and java_set are still implemented as m-files. 
On the other hand, the core are the builtin functions 
__java_get__ and __java_set__. 

Removing java_get.m and java_set.m 
and renaming __java_get__ and __java_set__ eases implementation 
and speeds it up a little bit. 


By the way: one has to explicitly remove java_get.m and java_set.m 
after make install. 
I consider this as a bug in the make process: 
The according directory shall be cleaned (retaining only java.opts and
javaclasspath.txt). 




    _______________________________________________________

Reply to this item at:

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

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