Re: [polyml] C++ standard in use

2017-12-23 Thread Florian Weimer
* Matthew Fernandez: > Full C++11 support arrived in GCC 4.8.1 [1] and Clang 3.3 [2]. C++11 support is still experimental in the 4.8 series. Feature-complete doesn't mean that it's production-ready. ___ polyml mailing list polyml@inf.ed.ac.uk

Re: [polyml] C++ standard in use

2017-12-21 Thread Matthew Fernandez
> On Dec 21, 2017, at 03:40, Makarius wrote: > > On 18/12/17 03:07, Matthew Fernandez wrote: >> >>> On Dec 16, 2017, at 03:24, Makarius >> > wrote: >>> >>> For Isabelle the situation is documented here: >>>

Re: [polyml] C++ standard in use

2017-12-21 Thread Makarius
On 18/12/17 03:07, Matthew Fernandez wrote: > >> On Dec 16, 2017, at 03:24, Makarius > > wrote: >> >> For Isabelle the situation is documented here: >> http://isabelle.in.tum.de/repos/isabelle/file/tip/Admin/PLATFORMS#l26 >> >> Presently

Re: [polyml] C++ standard in use

2017-12-17 Thread Matthew Fernandez
> On Dec 16, 2017, at 03:24, Makarius wrote: > > On 16/12/17 04:03, Matthew Fernandez wrote: >> >> Relatedly, coming up on 2018 it seems like it would be reasonable to require >> a compiler with C++11 support. I’m not sure how backwards compatible PolyML >> needs to be

[polyml] C++ standard in use

2017-12-15 Thread Matthew Fernandez
Hi David et al, While experimenting with some of the recent PolyML commits, I realised the build system doesn’t seem to set any particular C++ standard. I guess this results in the compiler default (e.g. GNU++14 in the latest GCC [0]). Is this intentional? Relatedly, coming up on 2018 it