|
Boost : |
From: Alain O' Miniussi (alain.miniussi_at_[hidden])
Date: 2024-03-28 22:59:42
Boost.MPI is based on Boost.Serialization. And I know a few people who uses Boost.MPI (starting with me).
I'm ok with moving to an alternative if there are suggestions but will need some time.
It also means that Boost.MPI will have to be removed from boost (as having a dependency outside of Boost and std woul be an issue I guess), but that can be considered if that's the only reason for extra maintenance work.
Cheers
---- Alain Miniussi DSI, Pôles Calcul et Genie Log. Observatoire de la Côte d'Azur Tél. : +33609650665 ----- On Mar 28, 2024, at 10:23 PM, Brook Milligan via Boost boost_at_[hidden] wrote: > Hi Robert, > > Iâm sorry you are feeling that Boost.Serialization might be EOL. I actually do > use it and have found its stability to be a great selling point over the years. > I confess that Iâm not a retro-compiler person so I personally donât use any > old compat code, but particularly in this case I expect many others might. Of > course, it is your decision I suppose, but it would be a great loss were the > library to be deprecated. > > Thanks for your steady work on it. > > Cheers, > Brook > >> On Mar 28, 2024, at 12:46 PM, Robert Ramey via Boost <boost_at_[hidden]> >> wrote: >> >> On 3/28/24 7:01 AM, Vinnie Falco via Boost wrote: >>> On Wed, Mar 27, 2024 at 2:34â¯PM Robert Ramey via Boost < >>> boost_at_[hidden]> wrote: >>> >>>> I would like to see suggestions as to how we could get usage statistics >>>> on boost libraries. >>>> >>> >>> Yes, this is an important area of analysis for which no perfect solution >>> exists. However, researchers at The C++ Alliance have developed an >>> experimental technique which offers hope for newly submitted libraries. >> >> Actually, I was thinking more of existing libraries. Case in point. I >> get relatively little feedback on the boost serialization library. It's >> been 20+ years. Initially it was almost alone. But now there are lots >> of alternatives. Serialization has never been proposed for the standard. >> It has few "stars" on github. I'm wondering if it's even used any more. >> It's becoming increasingly out of sync with evolving boost tools and >> hence more effort to maintain. Perhaps it's time to deprecated it or >> remove it from boost. >> >> Robert Ramey >> >> >> >> _______________________________________________ >> Unsubscribe & other changes: >> https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.boost.org%2Fmailman%2Flistinfo.cgi%2Fboost&data=05%7C02%7Cbrook%40biology.nmsu.edu%7C5a314fc4c5a3452aae7908dc4f5764f4%7Ca3ec87a89fb84158ba8ff11bace1ebaa%7C1%7C0%7C638472483990883482%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=O5Y%2BhZzW8iHnhDKizakgHg7GR762QF1KD8nOREuTDJ8%3D&reserved=0 > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk