On 04/29/2015 08:01 AM, Thierry Dumont wrote:
Le 29/04/2015 02:28, Volker Braun a écrit :
+1 to requiring C++11 support.
IMHO that added a number of really nice refinements of the language, if
you aren't using it yet for a C++ project then you are making a mistake.
+1
I am developing
Le 29/04/2015 02:28, Volker Braun a écrit :
+1 to requiring C++11 support.
IMHO that added a number of really nice refinements of the language, if
you aren't using it yet for a C++ project then you are making a mistake.
+1
I am developing extensively in C++: C++11 offers many interesting
+1 to requiring C++11 support.
IMHO that added a number of really nice refinements of the language, if you
aren't using it yet for a C++ project then you are making a mistake.
On Tuesday, April 28, 2015 at 4:23:25 AM UTC-4, Ralf Stephan wrote:
Hello,
with C++11 unique_ptr in a pynac
On 04/28/2015 10:23 AM, Ralf Stephan wrote:
So, is there any reason not to make C++11 mandatory in Sage?
This probably just implies SAGE_INSTALL_GCC=yes on more platforms.
Anyway, IMHO each package should check whether C++11 is supported.
(We'd still have to deal with that in some extension
On 28 April 2015 at 17:03, leif not.rea...@online.de wrote:
On 04/28/2015 10:23 AM, Ralf Stephan wrote:
So, is there any reason not to make C++11 mandatory in Sage?
This probably just implies SAGE_INSTALL_GCC=yes on more platforms.
Anyway, IMHO each package should check whether C++11 is
On Tuesday, April 28, 2015 at 6:03:26 PM UTC+2, leif wrote:
Anyway, IMHO each package should check whether C++11 is supported.
That may not be sufficient because headers from eg pynac are included
in cythonized files and so errors are generated there. When adding the C++11
switch to the
On Tuesday, April 28, 2015 at 6:03:26 PM UTC+2, leif wrote:
On 04/28/2015 10:23 AM, Ralf Stephan wrote:
So, is there any reason not to make C++11 mandatory in Sage?
(We'd still have to deal with that in some extension modules'
extra_compile_args(?) for a while.)
Ralf Stephan wrote:
On Tuesday, April 28, 2015 at 6:03:26 PM UTC+2, leif wrote:
Anyway, IMHO each package should check whether C++11 is supported.
That may not be sufficient because headers from eg pynac are included
in cythonized files and so errors are generated there. When adding
Latest NTL releases also require C++11.
--
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
