Boost Libraries and Dropping C++ Language Support
Glen Fernandes via Boost-announce <[email protected]> Wed, 22 Feb 2023 18:10:39 -0500
| Newsgroups | gmane.comp.lib.boost.announce,gmane.comp.lib.boost.devel,gmane.comp.lib.boost.user |
|---|---|
| Message-ID | <CAHVPgz=Rk-fXtVe9DMOQ0jh2Mdxjfy7d8NF4bmF-+i1LAXSJUA@mail.gmail.com> |
--===============2941166688386840128== Content-Type: multipart/alternative; boundary="000000000000c682d405f5520154" --000000000000c682d405f5520154 Content-Type: text/plain; charset="UTF-8" *Boost library authors and maintainers are free to drop support for old C++ standards in their libraries, at any time. * This includes libraries that other Boost libraries depend on. It even includes core libraries like Boost.Core or Boost.Static_Assert. We ask that maintainers do the right thing by all our users (which may include other Boost libraries) by announcing a future breakage *at least two Boost releases in advance*. When that eventual release time arrives, if Boost libraries are broken in older standards modes due to another Boost library dropping support, it will not block the Boost release. This means that we do not need to announce "Boost is dropping C++03" because Boost doesn't "support C++03" now as it is. It means that you, maintainer of Boost.X, should realize that you are free to announce that "Boost.X is dropping C++XY in version 1.Z" as you see fit. Boost in its infancy thrived because its libraries were on the cutting edge. Boost libraries today should similarly not be confined simply because other Boost libraries have chosen to depend on them. Furthermore, as Boost release managers we support authors exercising this freedom, and do not intend to impose any restrictions on what language support they must maintain. We will add a page to the Boost website stating the above formally. -- The release team (Glen Fernandes, Marshall Clow) --000000000000c682d405f5520154 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><b>Boost library authors and maintainers are free to drop = support for old C++ standards in their libraries, at any time. <br></b><br>= This includes libraries that other Boost libraries depend on. It even inclu= des core libraries like Boost.Core or Boost.Static_Assert.<br><br>We ask th= at maintainers do the right thing by all our users (which may include other= Boost libraries) by announcing a future breakage <b>at least two Boost rel= eases in advance</b>.<br><br>When that eventual release time arrives, if Bo= ost libraries are broken in older standards modes due to another Boost libr= ary dropping support, it will not block the Boost release.<br><br>This mean= s that we do not need to announce "Boost is dropping C++03" becau= se Boost doesn't "support C++03" now as it is. <br><br>It mea= ns that you, maintainer of Boost.X, should realize that you are free to ann= ounce that "Boost.X is dropping C++XY in version 1.Z" as you see = fit.<br><br>Boost in its infancy thrived because its libraries were on the = cutting edge. Boost libraries today should similarly not be confined simply= because other Boost libraries have chosen to depend on them.<br><br>Furthe= rmore, as Boost release managers we support authors exercising this freedom= , and do not intend to impose any restrictions on what language support the= y must maintain.<br><br>We will add a page to the Boost website stating the= above formally.<br><br>-- The release team (Glen Fernandes, Marshall Clow)= <br><div><br></div></div> --000000000000c682d405f5520154-- --===============2941166688386840128== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline