octave-maintainers
[Top][All Lists]
Advanced

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

Re: undeprecate java_set and java_get in stable branch?


From: Carnë Draug
Subject: Re: undeprecate java_set and java_get in stable branch?
Date: Sat, 12 Jul 2014 23:28:00 +0100

On 11 July 2014 16:05, Rik <address@hidden> wrote:
> On 07/10/2014 04:41 PM, address@hidden wrote:
>> Hi
>>
>> there was a short discussion on the bug tracker about undeprecating
>> the functions java_get and java_set [1].
>>
>> The arguments boils down to that we should not be deprecating things
>> when there is no alternative to them yet. We hope that there will be a
>> replacemente for them in 4.2 but that replacement does not exist yet
>> and what can developers use in versions 3.8 and 4.0?
>>
>> Should we undeprecate these in the stable release? This does not
>> change anything, only that there's no warning about them being
>> deprecated when actually they are not anymore.
> I support this.  Until we have a solid replacement that works with static
> class variables we should keep these two functions around.  Later on we can
> decide if we want to keep them as a permanent part of Octave or not, but
> for now they seem important.

Done. See http://hg.savannah.gnu.org/hgweb/octave/rev/54ab08d8de55

Carnë



reply via email to

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