> On 27 Mar 2018, at 5:52 pm, Ken Cunningham <[email protected]> > wrote: > > > On 2018-03-27, at 7:43 AM, Benjamin Redelings wrote: > > >> I suppose there could be a c++14 portgroup? > > There could be. > > But I would instead propose that MacPorts never puts forward a compiler that > can't handle c++14 at this point in time instead.
Agreed, but what about c++17 ? And then the next standard, and so on. This is an issue that isn’t going to go away with just 11, or 14... > > If the system-installed clang is new enough to support c++14, OK. Otherwise > default to clang-5.0 instead. > > I see no need to prospect that capabilities of ancient clang versions nobody > cares about any more. > > or similar.
