Hello,
with C++11 unique_ptr in a pynac develment version I get in Sage:
gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/home/
ralf/sage/local/include -I/home/ralf/sage/src
-I/home/ralf/sage/src/c_lib/include
-I/home/ralf/sage/src/sage/ext -I/home/ralf/sage/local/lib/python2.7/site-
packages/numpy/core/include -I/home/ralf/sage/local/include/python2.7 -c
build/cythonized/sage/symbolic/getitem.cpp -o build/temp.linux-x86_64-2.7/
build/cythonized/sage/symbolic/getitem.o -fno-strict-aliasing -w -fno-tree-
dominator-opts
In file included from ../local/include/pynac/pseries.h:27:0,
from ../local/include/pynac/ginac.h:46,
from build/cythonized/sage/symbolic/ginac_wrap.h:11,
from build/cythonized/sage/symbolic/getitem.cpp:350:
../local/include/pynac/expairseq.h:161:2: error: ‘unique_ptr’ in namespace ‘
std’ does not name a type
pynac master already introduces C++11 code internally (typeid.hash_code()
is C+11)
but will require it also for Sage with a pending commit because of included
headers
containing the bugfree auto_ptr replacement unique_ptr.
Now, I can maintain a pynac branch with auto_ptr indefinitely but would not
like to.
It's not that C++11 is bleeding edge, there is already C++14 (released on
December 15,
2014) and C++17.
So, is there any reason not to make C++11 mandatory in Sage? The way to do
it is this m4 macro:
https://www.gnu.org/software/autoconf-archive/ax_cxx_compile_stdcxx_11.html
Regards,
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
