|
Boost : |
From: Nelson, Erik - 2 (erik.l.nelson_at_[hidden])
Date: 2024-07-29 15:00:25
Vinnie Falco Sent Sunday, July 28, 2024 8:49 PM
>We need to be careful here. Consider Boost.JSON. It implements a
>variant-like, mutable container which can hold a JSON document. Is there
>room for other JSON libraries in Boost? Why yes, there are. For example,
>SIMDJson uses a completely different approach. It is read-only and it makes
>a different set of tradeoffs.
>When I say that if both libraries are useful, they should both be
>considered for inclusion, we must carefully define "useful." If two
>libraries offer a set of features, or if the two libraries make different
>tradeoffs to the extent that such tradeoffs result in different and
>meaningful user bases, then both could be considered.
Exactly right, witness Statechart and MetaStateMachine (MSM) with different design goals. This topic was much discussed during the MSM review, as author Cristophe Henry notes in the Stackoverflow link below.
https://stackoverflow.com/questions/4275602/boost-statechart-vs-meta-state-machine
----------------------------------------------------------------------
This message, and any attachment(s), is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/electronic-disclaimer. If you are not the intended recipient, please delete this message. For more information about how Bank of America protects your privacy, including specific rights that may apply, please visit the following pages: https://business.bofa.com/en-us/content/global-privacy-notices.html (which includes global privacy notices) and https://www.bankofamerica.com/security-center/privacy-overview/ (which includes US State specific privacy notices such as the http://www.bankofamerica.com/ccpa-notice).
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk