octave-maintainers
[Top][All Lists]
Advanced

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

Re: "features" problems


From: John W. Eaton
Subject: Re: "features" problems
Date: Thu, 10 Mar 2016 17:42:57 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0

On 03/10/2016 05:30 PM, Carnë Draug wrote:
On 10 March 2016 at 22:21, John W. Eaton <address@hidden> wrote:
[...]
I recently changed the layout of the structure returned by
octave_config_info.

Instead of writing

   octave_config_info ("features").JAVA

I recommend writing

   __have_feature__ ("JAVA")

as that will work with the new and old structure layouts.


Should we make use of this private and internal functions outside core?

And since octave_config_info() was not a private function, if we want to
change this, should we not deprecate "features" first?

The whole point of not using a private function is that their behaviour will
not change suddenly.

Yeah. Unfortunately, the layout of the structure returned by octave_config_info wasn't very good.

Probably octave_config_info should have been tagged as a "system"/"private" function as well.

jwe





reply via email to

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