Date: Wed, 31 Jan 2024 19:22:07 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 276738] clang: static_assert conflicts with -std=c++98 -pedantic-errors Message-ID: <bug-276738-29464-gPbMYtRBqW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-276738-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-276738-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276738 --- Comment #5 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Henri Menke from comment #2) My notes on interpreting this: "it doesn't say anywhere explicitly that C++98 is unsupported.": listing everything not supported is highly unusual and would be a big effort. Normally if support is not mentioned, it is not supported and what is explicitly supported is explicitly mentioned. The lack of a page https://libcxx.llvm.org/DesignDocs/ExtendedCXX98Support.= html is also highly suggestive of lack of C++98 support. Even https://libcxx.llvm.org/DesignDocs/ExtendedCXX03Support.html says for C++03: QUOTE Clang provides a large subset of C++11 in C++03 as an extension. END QUOTE (Again, an explicit mention of the partial support.) But C++03 is after C++ 98 as well and that note does not imply anythign for the C++98 status. I fully agree that having a error report that was in terms of static_assert notation would be far better error handling than what now happens. But an error report of some kind should be what happens as far as I can tell. Being C++ backwards compatible is messier than for C generally. It is unlikely FreeBSD would taken on such for C++ subjects where upstream does not. Quality of error messages where FreeBSD code contributes to why the message is odd is something FreeBSD is more likely to deal with. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276738-29464-gPbMYtRBqW>