octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #55361] ((octave-forge)[control] build errors


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #55361] ((octave-forge)[control] build errors due to removed features in Octave-6.0.0
Date: Wed, 2 Jan 2019 07:40:17 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

Follow-up Comment #2, bug #55361 (project octave):

@JohnD:
The relevant features were deprecated in (IIRC) 3.8 or 4.0, and AFAICS JWE
replaced them by OCTAVE_DEPRECATED macros that effectively translated the
deprecated calls into the new forms after emitting a suitable message.
So yes I think they should work in 5.0.0.
To be sure, later today I'll try to cross-build 5.0.0 (couldn't do that until
yesterday due to an incomplete fix for bug #55306 that wasn't merged into
default yet so I could build 6.0.0), but I expect no problems.

FYI:
As to e.g., is_numeric_type() => isnumeric() and similar changes, Olaf Till
patched the io package for me so that configure would replace the macros in
the code (csv2ell() ) with the required forms for the Octave release used to
install the package. That way the io package would also work with older (IMO
ancient) Octave releases.
I've got mixed feelings about this. IMHO users (and for that matter, some
distros) should just upgrade to a newer Octave release rather than implicity
leave a maintenance burden on OF developers, but I'm not the one who will
block this - after all Olaf took up the work.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55361>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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