[Top][All Lists]

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

[Octave-bug-tracker] [bug #57585] [octave-forge] (image) deprecation war

From: Carnë Draug
Subject: [Octave-bug-tracker] [bug #57585] [octave-forge] (image) deprecation warnings during installation (compilation) of image package
Date: Tue, 14 Jan 2020 13:57:29 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #4, bug #57585 (project octave):

Mike Miller wrote:
> FWIW, I have added "-Wno-deprecated-declarations" to the signal package
src/Makefile to avoid these types of warnings when users install the package.
I think it makes sense to ship packages with this diagnostic disabled to
prevent users from being distracted by these warning messages.
> I think this warning message is very useful for maintainers and developers,
but distracting and unhelpful for users installing the package from source.

I get this.  However, I feel in that practice what will happen is that even
maintainers and developers will end up building with those warnings disabled
and then get caught by surprise when it's too late.

By not disabling the warnings, hopefully maintainers and developers will catch
them before the Octave release and so normals users, who don't build from
development sources, won't even get to see the warnings.

Anyway, I have a local patch that fixes this for most cases.  I'm just unsure
what to do when the error is coming from inside some C++ classes in the image
package. Is there any documentation about what happens at all? I see nothing
on the manual and on doxygen. I'm guessing that octave_value is throwing some
exception when the conversion for a type fails and that the interpreter is
catching them. Is that correct? What is that, how do I catch them and can a
package also throw them?


Reply to this item at:


  Message sent via Savannah

reply via email to

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