octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Make java2mat an internal function only?


From: Rik
Subject: Re: Make java2mat an internal function only?
Date: Wed, 28 Mar 2018 13:41:59 -0700

On 03/28/2018 05:28 AM, address@hidden wrote:
Subject:
Re: Make java2mat an internal function only?
From:
siko1056 <address@hidden>
Date:
03/27/2018 01:36 PM
To:
address@hidden
List-Post:
<mailto:address@hidden>
Content-Transfer-Encoding:
quoted-printable
Precedence:
list
MIME-Version:
1.0
References:
<address@hidden>
In-Reply-To:
<address@hidden>
Message-ID:
<address@hidden>
Content-Type:
text/plain; charset=UTF-8
Message:
2

Rik-4 wrote
All,

I notice that java2mat has no documentation, just "Undocumented internal
function".

Using grep, I can't see that it is used anywhere in the core either. 
Should we rename this to "__java2mat__" to indicate that it really is an
internal function?  Eventually we could even deprecate it if no one is
using it, but I would start with renaming it.

--Rik
Agree to rename this to "__java2mat__".  This function is there since the
integration of the java package to core [1].  I cannot figure out a
meaningful purpose.  It seems to somehow extract an double array to Octave
using the C++ function "box_more", that is not undocumented as well, and
only used from "java2mat".
Okay, I deprecated java2mat and made the C++ function available as __java2mat__.  I put a message in the help text for java2mat to file a bug report if they are using this function and can't find a way to do what they need with other Octave functions.  I doubt anyone is using this, but it is a big world and you never know.

--Rik

reply via email to

[Prev in Thread] Current Thread [Next in Thread]