[Octave-bug-tracker] [bug #38725] Empty javaclasspath returns non-empty cell array

[Philip Nienhuis]

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

                 Summary: Empty javaclasspath returns non-empty cell array
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Fri 12 Apr 2013 08:15:22 PM CEST
                Category: Libraries
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

Using stable Octave and the Java package I get:


octave-3.6.4-rc1:4> jcp = javaclasspath
jcp = {}(0x0)


... while with the dev version I get:

octave:29> jcp = javaclasspath
jcp =
{
  [1,1] =
}


Obviously it would be hard to check what ML does (as its javaclasspath is
preloaded with order of 200 entries after startup).

Is there a reason that an empty javaclasspath now returns a non-empty cellstr
array? (= with one empty cell)

I'd rather prefer the old behavior, i.e., returning a completely empty cellstr
array.

I'll submit another (minor) bug with javaclasspath in an other bug tracker
entry. I doubt if they are related, but you never know...




    _______________________________________________________

Reply to this item at:

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

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