[Top][All Lists]

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

[Octave-bug-tracker] [bug #55266] deprecation warning about octave::eval

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55266] deprecation warning about octave::eval_string just for including parse.h
Date: Fri, 28 Dec 2018 18:03:04 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Update of bug #55266 (project octave):

                  Status:               Confirmed => Patch Submitted        


Follow-up Comment #5:

The cleanest way I can see to solve this is to make the inline eval_string
deprecation wrappers from Octave 4.4 into compiled functions again, as in the
attached diff. With this change on the stable branch, Octave compiles cleanly
without warnings and parse.h can be included in user code without any
deprecation warnings.

I'll push this after a little more testing here, please object if needed.

AFAICT this is the only deprecation wrapper that called something which was
subsequently deprecated in Octave 5. I went through all individual header
files and reported a separate bug on type errors (bug #55277), but I haven't
seen any other inadvertent deprecation warnings in the public API.

(file #45765)

Additional Item Attachment:

File name: parse.diff                     Size:2 KB


Reply to this item at:


  Message sent via Savannah

reply via email to

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