[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53280] Eliminate C++0X workarounds now that C
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #53280] Eliminate C++0X workarounds now that C++11 is required |
Date: |
Mon, 5 Mar 2018 11:53:06 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Update of bug #53280 (project octave):
Category: Documentation => Configuration and Build
System
Item Group: Documentation => Other
Status: None => Confirmed
Release: 4.2.1 => dev
Summary: Confusing documentation. => Eliminate C++0X
workarounds now that C++11 is required
_______________________________________________________
Follow-up Comment #2:
Actually, this isn't just a documentation bug. On the development branch
C++11 is now required. Any references to C++0X should be fixed, and then the
FIXME notes removed.
Using grep I find three instances of C++0X that need resolution.
array/Array.h:898: // FIXME: this would be simpler once C++0x is available
corefcn/call-stack.cc:37:// NOTE: C++0x will allow these two to be merged into
one.
corefcn/gcd.cc:60:// implements template aliases from C++0x, can do a small
fix here).
I will try to get this added to the OctConf 2018 agenda for one of the code
sprints.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53280>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/