February 2023 - Boost - lists.boost.org

CMake Announcement from Boost Steering Committee
by Jon Kalb 13 Aug '24

13 Aug '24

The libraries produced by the Boost community have had a greater impact on the way that the C++ community writes code than any other library implementation. The focus of the Boost community will always be on the libraries, but it is undeniable that we are dependent on and often limited by the infrastructure of our trade. Years ago, the move to Git was contentious; yet, it was required to improve development. In a similar vein our build system has become an impediment for many developers and users, existing and prospective. Therefore, we, the Steering Committee, announce to the Boost community our desire and intent to move Boost’s build system to CMake for users and developers alike. We are soliciting comments and proposals from the community to guide the process and the goals. Our desire is that the community can come to consensus by the end of the calendar year with a vision of supporting users and developers. We understand that the actual process of achieving the end goal will be long, time consuming, and not without its share of conflict. We also recognize that the Boost community is comprised of bright and passionate individuals that are eager to get involved and help get work done. The members of the Steering Committee have been encouraged by the discussions and activity surrounding CMake on the mailing lists over the years and know that many people have voiced visions. We hope that each of you rejoins the discussion to support this initiative and contributes to the common goal of improving Boost’s integration into the broader C++ ecosystem. For the Boost Steering Committee, Jon Kalb, Chair jonkalb(a)boost.org

49 200

Boost Governance?
by René Ferdinand Rivera Morell 10 Aug '24

10 Aug '24

A disclaimer: I write this solely as a Boost Library author. And not in any other capacity or representing any other interest. It's now been at least a year since Boost switched from the Software Freedom Conservancy to the Boost Foundation for its governance organization. But have people noticed any difference? Did you know that switch happened? Did you know that they held an election for the Board of Directors and for the Officers? Do you know when that election happened? Do you know who got elected? Do you know how they were selected? Do you know what their responsibilities are? Do you know what their bylaws are? Do you know their financials? More importantly: Did you answer "no" to any of those questions? As a library author, I can say I definitely answered no to many of those questions. This is a problem. As authors, without asking, we should know those answers from the organization that governs our work. We should have input into how that organization governs. In other words, we deserve open and transparent governance; not the closed and opaque status quo. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

10 10

Paul Bristow
by John Maddock 09 Aug '24

09 Aug '24

I've just heard that Paul Bristow who helped so much with the development of Boost.Math and indeed many other libraries, passed away peacefully last week. RIP Paul. Much missed. John.

7 7

Library proposal - indexed_array
by Julien Blanc 12 Oct '23

12 Oct '23

Hi, I've written and released a (rather small) library which allows defining arrays with arbitrary index mechanisms (hence the name, indexed_array). This especially allows indexing with scoped enums, use non zero-starting indexes, or use sparse indexes. This is not a view, but an array in the sense that it owns the data, and provides the same guarantees and functionalities as std::array, such as triviality propagation, being able to reside in read-only program sections, etc. It also supports multidimensional indexing, and provides an indexed_span template class to access lower dimension content (which can be used outside indexed_array). Finally, it provides an opt-in safer way to initialize the array content, which is especially useful when using complex and/or changing indexing schemes (like based on externally generated files). The library is available here: https://github.com/Julien-Blanc-tgcm/indexed_array And the doc is here: https://julien-blanc-tgcm.github.io/indexed_array/ It requires C++17 and mp11, and has first-class support for describe-d enums. If there is some interest, i'd like to propose it for inclusion in boost. So i'm looking for people who would endorse it. Thanks and best regards, Julien

8 24

improve <boost/config.hpp>
by Gero Peterhoff 03 Mar '23

03 Mar '23

Hi, for more compatibility with existing boost-macros/defines I came up with - see attachment. 1) Is that correct in principle? 2) Problem: for BOOST_NO_CXX23_HDR_XXX I use __has_include. However, __has_include is not guaranteed to exist. How about the solution? 3) Did I miss useful things? thx Gero

6 6

Has testing on msvc been dropped?
by Daniela Engert 01 Mar '23

01 Mar '23

Hi y'all! I've noticed that e.g. Boost.Log no longer compiles on msvc 19.35 (i.e. VS2022 update 5). Looking at the test matrix to figure out where the problem might lie, I couldn't find any column with the test results of *any* msvc version, lest the current one. Is there a reason for no longer running the tests with msvc compilers? thank, Dani -- PGP/GPG: 2CCB 3ECB 0954 5CD3 B0DB 6AA0 BA03 56A1 2C4638C5

6 21

Re: [boost] Delivery Status Notification (Failure)
by Andre Marin 27 Feb '23

27 Feb '23

Hi, I'm interested in becoming a maintainer. I'm interested in the following projects: - Algorithm <https://www.boost.org/doc/libs/release/libs/algorithm/> - Python <https://www.boost.org/doc/libs/release/libs/python/> - Stl_interfaces <https://www.boost.org/doc/libs/release/libs/stl_interfaces/> - Type Erasure <https://www.boost.org/doc/libs/release/libs/type_erasure/> I'm trying to email olivas(a)icecube.umd.edu, per the Boost website but it's not going through. I'm looking for some guidance. I've included the previous request and email error in this email. Thank you, *Andre Marin * *m:* (832) 495-3545 *e:* andre(a)alexamarin.com <https://www.linkedin.com/in/andremarin629/> On Sun, Feb 26, 2023 at 11:46 AM Mail Delivery Subsystem < mailer-daemon(a)googlemail.com> wrote: > [image: Error Icon] > Address not found > Your message wasn't delivered to *olivas(a)icecube.umd.edu* because the > address couldn't be found, or is unable to receive mail. > The response from the remote server was: > > 550 5.1.1 <olivas(a)icecube.umd.edu>: Recipient address rejected: User > unknown in local recipient table > > > > ---------- Forwarded message ---------- > From: Andre Marin <andre(a)alexamarin.com> > To: olivas(a)icecube.umd.edu > Cc: > Bcc: > Date: Sun, 26 Feb 2023 11:46:03 -0600 > Subject: Boost Library Official Maintainer Program > Hi, > > I'm interested in becoming a maintainer. I'm interested in the following > projects: > > - Algorithm <https://www.boost.org/doc/libs/release/libs/algorithm/> > - Python <https://www.boost.org/doc/libs/release/libs/python/> > - Stl_interfaces > <https://www.boost.org/doc/libs/release/libs/stl_interfaces/> > - Type Erasure > <https://www.boost.org/doc/libs/release/libs/type_erasure/> > > > I've been limited to C++11 at work and I'm new to library contributions. > I'm not sure if there are more appropriate projects for noobs or areas of > need I couldn't find on the website. > > Thank you, > > *Andre Marin * > *m:* (832) 495-3545 > *e:* andre(a)alexamarin.com > <https://www.linkedin.com/in/andremarin629/> >

2 1

Future of boost::TypeTraits
by Gero Peterhoff 24 Feb '23

24 Feb '23

Hello, with the planned changes of the dependencies of the boost libraries to newer C++-standards, I would like to ask how this is planned for boost::TypeTraits. 1) In my opinion it would make sense to remove all TypeTraits that are already in the standard, and only provide those that do not exist in the standard (yet). Of course, this depends on the planned minimum standard for boost::TypeTraits. 2) If, on the other hand, boost::TypeTraits is to continue to work with C++03 (for which there may be reasons), however, quite a few adjustments must be made (for newer C++-standards) and bugs must be fixed. Examples: a) - no inline-variables are provided for C++17 (if useful), e.g. is_arithmetic_v - no concepts are provided for C++20 (if useful), e.g. arithmetic - that's why I already asked how to do this best without coming into (name)conflicts with existing structures/namespaces/etc. b) bugs - e.g. is_integral does not contain char8_t (if available) Probably my remarks also apply to other libraries, possibly TypeErasure, TypeIndex, TTI ... All this has to be reworked fundamentally and consolidated if necessary. best regards Gero

1 0

Boost Libraries and Dropping C++ Language Support
by Glen Fernandes 24 Feb '23

24 Feb '23

*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)

8 12

Boost 1.82.0 is now closed for new libraries and breaking changes
by Marshall Clow 23 Feb '23

23 Feb '23

Next deadline: On 1-Mar-2023 Boost 1.82.0 closes for major code changes. Still open for serious problem fixes and docs changes without release manager review. As always, the release calendar is at https://www.boost.org/development/ <https://www.boost.org/development/> - Boost release team

1 0

Fwd: Futex using boost, threads never wakeup
by tsoumplekas_giorgos 23 Feb '23

23 Feb '23

Subject: Futex using boost, threads never wakeup Hello all I posted the following question in stackoverflow https://stackoverflow.com/questions/75538799/futex-using-boost-threads-neve… 0 <https://stackoverflow.com/posts/75538799/timeline> I am studying about futex synchronisation Following up the manual <https://man7.org/linux/man-pages/man2/futex.2.html> , I tried to syncroniaze threads using boost futex However the threads never wake up #include <iostream>#include <atomic>#include <boost/fiber/detail/futex.hpp>#include <thread>#include <vector>#include <chrono>void wait(std::atomic<int> & futexp){ int one = 1; while(std::atomic_compare_exchange_strong(&futexp, &one, 0)) {} std::cout << std::this_thread::get_id() << "," << futexp.load() << std::endl; boost::fibers::detail::futex_wait(&futexp,0); // std::this_thread::sleep_for(std::chrono::milliseconds(5000)); }void fpost(std::atomic<int> & futexp){ int zero = 0; if (std::atomic_compare_exchange_strong(&futexp, &zero, 1)) { boost::fibers::detail::futex_wake(&futexp); } } std::atomic<int> futexp{1};int main() { std::vector<std::thread> vec; for(int i =0 ; i< 5;++i) { vec.emplace_back([]() { wait(futexp); fpost(futexp); }); } Code demo <https://godbolt.org/z/94hMsrW4a> I am using boost 1.66 and gcc 9.1 What goes wrong with this piece of code ?

3 2

Boost 1.82 closing for new libraries and breaking changes on 2023-02-24
by Glen Fernandes 22 Feb '23

22 Feb '23

On 02/24: Release branch will close for new libraries and breaking changes to existing libraries. Will still be open for bug fixes and other routine changes to all libraries without release manager review.

1 0

Dropping C++03 support (again)
by Peter Dimov 21 Feb '23

21 Feb '23

Greetings, I have a novel idea, let's drop C++03 support. The reasons to do that have been explicated already a number of times, e.g. in https://pdimov.github.io/articles/phasing_out_cxx03.html#_ongoing_costs_of_… but in brief: * C++03 is 20 years old. * A number of intra-Boost dependencies can be eliminated by using the standard equivalent of Boost components. This will help Boost to become "more modular". * Variadic templates allow us to remove the uses of Preprocessor and MPL, which are the primary contributor to slow Boost compilation times. * Almost no new C++03 development occurs in Boost at this point, so C++03 users do not need to upgrade their Boost. To that end, I propose the following: Boost release 1.82.0 is announced as the last one with C++03 support. If critical problems are found in it post-release, we will issue 1.82.1, 1.82.2 and so on, as appropriate (as C++03 users will not be able to just upgrade to 1.83.) Boost release 1.83.0 is announced to require C++11 at minimum. This means compilers that have all the C++11 standard headers, and support all the C++11 syntactic constructs and keywords without issuing errors. (E.g. VS2013 doesn't qualify because it doesn't support the `constexpr` or `noexcept` keywords.) This proposal should ultimately be approved and implemented by the Boost release managers; their opinions are particularly appreciated.

28 98

Mustache has been REJECTED from boost.
by Klemens Morgenstern 21 Feb '23

21 Feb '23

First I want to thank Peter for the submission and all reviewers for their participation in the review process. Please note that votes don't just get added up, but that details of every review, especially the time & effort spent on it, will influence how reviews get weighed. This review was close, with 3 REJECT, 4 Conditional ACCEPT and 0 ACCEPT votes. Rene, Jens and Darryl voted to accept on the condition that the documentation shall be improved/completed. Ruben's review had more complex conditions, among them this one: > 1. The partials argument must be typed according to the data structure it requires. Peter's response to this was "I don't see how this is supposed to be accomplished." I don't know what to make of the technical details here, but I don't think I can make something that might be impossible to accomplish a condition for acceptance. Julien & Vinnie voted to REJECT based on the state of the library, which makes me believe they might change their vote in a future review. Dmitry voted to REJECT based on the mustache language itself, and thus was the only one to reject boost.mustache in general. Based on the almost even split between conditional accept & reject and the lack of unconditional accepts, I decided to REJECT the library at this time. I hope Peter will submit an improved & extended version of this library for review in the future.

6 6

macro BOOST_HAS_CONCEPTS not work + namespace for concepts
by Gero Peterhoff 20 Feb '23

20 Feb '23

Hi, 1) the macro BOOST_HAS_CONCEPTS from <boost/config.hpp> (https://www.boost.org/doc/libs/1_81_0/libs/config/doc/html/boost_config/boo…) not work: https://godbolt.org/z/3G8vTrjcf 2) namespace for concepts Would it make sense to introduce a namespace *only* for concepts to avoid naming conflicts with existing classes? boost::concepts would be useful, but this is already used by the concept-check-library. Then would boost::Concepts be a good choice or could boost::concepts still be used? EG namespace boost { template <typename Type> struct my_trait ...; #if !defined(BOOST_NO_CXX17_INLINE_VARIABLES) template <typename Type> inline constexpr bool my_trait_v = my_trait<Type>::value; #endif #if concepts available namespace Concepts { template <typename Type> concept my_concept = my_trait_v<Type>; } // Concepts #endif } // boost thx Gero

4 10

Review of mustache starts today.
by Klemens Morgenstern 19 Feb '23

19 Feb '23

The formal review of the mustache starts today, Sunday the 5th, and ends next week on Tuesday the 14th. The library was developed & submitted by Peter Dimov. Boost.Mustache is an implementation of Mustache templates in C++11. The master branch is frozen during the review and can be found here https://github.com/pdimov/mustache The current documentation can be found here: https://pdimov.github.io/mustache/doc/html/mustache.html Boost.Mustache is an implementation of Mustache templates in C++11. The documentation of Mustache templates is here: https://mustache.github.io/ Review ======== Please explicitly state that you either *accept* or *reject* the inclusion of this library into boost. The accept can be conditional. Also please indicate the time & effort spent on the evaluation and give the reasons for your decision. The review is open to anyone who is prepared to put in the work of evaluating and reviewing the library. Prior experience in contributing to Boost reviews is not a requirement. Some questions to consider: - Does this library bring real benefit to C++ developers for real world use-case? - Do you have an application for this library? - Does the API match with current best practices? - Is the documentation helpful and clear? - Did you try to use it? What problems or surprises did you encounter? - What is your evaluation of the implementation? More information about the Boost Formal Review Process can be found at: http://www.boost.org/community/reviews.html Reviews can also be submitted directly to me. Thank you Peter for submitting yet another boost library & thanks for all the reviews in advance. Building boost.mustache ======================= Here's how to build the library, starting from scratch: 1. Clone Boost from Github: git clone --recurse-submodules https://github.com/boostorg/boost 2. Clone the Mustache library into the Boost tree: cd boost/libs git clone https://github.com/pdimov/mustache cd .. 3. Build b2: ./bootstrap.sh (We assume Linux and g++ from now on. On Windows, it's just `booststrap`.) 4. Generate the header links in the boost/ directory: ./b2 headers 5. Build the Mustache library and its dependencies (e.g. JSON): ./b2 --with-mustache This will place the compiled libraries into the stage/lib directory. It should contain libboost_container.a/.so, libboost_json.a/.so, and liboost_mustache.a/.so. You can now build and run the Mustache examples by using e.g. g++ libs/mustache/example/html.cpp -o html -I . -L stage/lib -lboost_mustache -lboost_json ./html

20 60

boost::math::tools::promote_args not works with C++23 FP-types
by Gero Peterhoff 19 Feb '23

19 Feb '23

Hi, promote_args from <boost/math/tools/promotion.hpp> not works with new/extended C++23 FP-types https://godbolt.org/z/13fq8a3d7 The problem might be the outdated "manual variadic" implementation for C++03. Well, according to the documentation (https://www.boost.org/doc/libs/1_81_0) boost::math requires C++11 anyway; with a switch to C++11 it also works (std::common_type). This issue also affects some implementations in boost::math::policies. PS: We have (at least) 3 different definitions for the *same* boost::float128(_type/_t) type 1) <boost/config.hpp>: boost::float128_type 2) <boost/math/cstdfloat/cstdfloat_types.hpp>/<boost/math/cstdfloat/cstdfloat_cmath.hpp>: BOOST_CSTDFLOAT_FLOAT128_NATIVE_TYPE/float128_t 3) <boost/math/tools/config.hpp>: BOOST_MATH_FLOAT128_TYPE :-( thx Gero

3 2

Mustache review has ended
by Klemens Morgenstern 19 Feb '23

19 Feb '23

The review of Mustache has ended, thanks to everyone who wrote a review! I would also like to thank the review wizards for granting the extension. That really helped to get us more reviews. I'll try to announce the review results soon, but please note that this is another close call that will need some careful consideration.

2 1

Release Notes: Markdown to replace QBK
by Vinnie Falco 18 Feb '23

18 Feb '23

We need to re-render all of this historical release notes, such as: <https://www.boost.org/users/history/version_1_81_0.html> to be in the style of the new website. This is being taken care of, but it will affect the release process as follows: * Each author will edit the release notes for their library using markdown instead of Quickbook format, as a pull request against a file here: <https://github.com/boostorg/website/tree/master/feed/history> The syntax will be GitHub flavored markdown, with a few Boost-specific extensions (for example, to link against an issue in a boostorg repo). Does anyone object or have comments about this? -- Regards, Vinnie Follow me on GitHub: https://github.com/vinniefalco

7 21

[mustache review] Period has been extended until the 18th
by Klemens Morgenstern 17 Feb '23

17 Feb '23

Due to the few reviews and the overlap with the WG21 meeting I have successfully petitioned the review wizards to extend the review period until next Saturday, the 18th of february. Please consider writing a boost.mustache review, since only two have been submitted up to now.

2 2

boost.mustache review reminder (ends this saturday)
by Klemens Morgenstern 14 Feb '23

14 Feb '23

This is a reminder that the boost.mustache review is currently going on and will end this saturday. Please consider submitting a review.

1 0

GSoC 2023 ideas proposals
by David Bellot 13 Feb '23

13 Feb '23

Hi everyone, Boost C++ is candidating again this year to be part of the Google Summer of Code 2023. Each year we are honoured to have students and contributors joining us for the summer and being sponsored by Google. Again, this year, I will ask for all the mentors who are interested in ... well... mentoring a student or contributor, to help us and write their ideas in this document: https://github.com/boostorg/wiki/wiki/Google-Summer-of-Code:-2023 It will help our future students to choose, to develop their own proposal and to be part of our Boost journey. Best regards, David

1 0

[mustache] The docs
by Andrzej Krzemienski 09 Feb '23

09 Feb '23

Hi Everyone, I wanted to share my initial thoughts after reading the docs for the proposed Boost.Mustache. If some library docs said "I am implementing JSON", I more-less know what to expect, because JSON is popular, I used it, so one can reliably predict what the library delivers. This is not the case with Mustache. It is the first time I have heard this name. Apparently, it is a less popular thing. Therefore, I would expect some more introduction than just an external link. The linked page also doesn't contain sufficient information but further links. For instance to https://mustache.github.io/mustache.5.html, but this information also doesn't help me find answers to my questions: 1. What is considered an "optional part" of mustache? Boost.Mustache says it only implements the non-optional parts, but docs in mustache(5) do not indicate the optional parts. 2. It is clear to me that the procedure takes a template (with mustaches) and the data to be replaced. But what is the range of the acceptable formats of this data? The examples show that it is JSON, but does it have to be JSON? Boost.Mustache docs say it could be 'described' classes? But is that all? How about Boost.PropertyTree? What does the specification for Mustache say about it? 3. I do not see any specification (neither in Boost.Mustache docc, nor in the linked mustache(5)) for what is the required behavior when I have nested mustashes with the same name, or a JSON file with nested elements of the same name. Or did I miss this description? Regards, &rzej;

5 17

Boost.Buffers: network-agnostic buffer types and algorithms
by Vinnie Falco 07 Feb '23

07 Feb '23

Greetings. I am asking if there is any interest in a Boost.Buffers library, which consists of the following: * ConstBuffer, MutableBuffer concepts * ConstBuffers, MutableBuffers concepts * const_buffer, mutable_buffer types * DynamicBuffer concept * `source` and `sink` abstract interfaces used to define the Source and Sink concepts * metafunctions for checking all type requirements * implementations of common buffers and dynamic buffers: - buffers_pair - array_of_buffers - circular_buffer - dynamic_string_buffer * Algorithms: - buffer_copy - buffer_size The twist is that this library has no dependency on Asio or Boost.Asio (but Asio will still recognize them thanks to some template heroics and a splash of forward declarations). Why am I proposing this? Well, let me tell you some things... I am currently working on these two libraries: Boost.Http.Proto Boost.Http.Io The Proto library implements HTTP/1 to a fuller feature set than Beast and fixes all the design flaws in Beast (but it is completely not API compatible). This library does not do any network I/O, it is expressed purely in terms of buffer concepts (i.e. depends on Boost.Buffer and not Boost.Asio). The Io library depends on Asio and the Proto library to provide the network algorithms which use Asio to implement HTTP/1. This is the equivalent HTTP functionality of what Beast offers today. Websockets is not included but when I am done with Http I will redo websockets with improvements and new features, and similarly they will be developed as two libraries: Boost.Websockets.Proto Boost.Websockets.Io My motivation for splitting libraries this way is as follows: * Each library is smaller and compiles more quickly * CI turnarounds are faster * Separation of concerns The HTTP Protocol library is designed in a way that much of an application's HTTP business logic can be expressed independently of Asio using only the constructs found in Http.Proto. This especially means fewer templates and faster compilation because Http.Proto is designed from the ground up to avoid templates whenever possible. However during the development of Http.Proto I find myself having to reach for the same buffer algorithms and containers that I developed for Beast (such as the circular buffer and the dynamic buffer). So Http.Proto has been steadily growing these things: <https://github.com/CPPAlliance/http_proto/blob/a3a284f06597ad12ca6cc1782beb…> Extract this independent buffer functionality into a separate library Boost.Buffers would bring these benefits: * Again a smaller library, faster compilation * Faster CI turnarounds * Separation of concerns Additionally, algorithms can be expressed in terms of asio-independent buffer types and concepts. For example, Boost.JSON could implement the boost::buffers::sink and boost::buffers::source interfaces which would enable its use in Boost.Http.Proto and Boost.Requests (an upcoming HTTP client library from Klemens), without having to depend on either of those libraries or Asio. Is this style of development of smaller, fine grained libraries that separate concerns something that is desirable for Boost? Glad for any feedback. -- Regards, Vinnie Follow me on GitHub: https://github.com/vinniefalco

11 29

Interest in cpp-member-accessor?
by Hans Dembinski 07 Feb '23

07 Feb '23

Dear all, Hubert Liberacki wrote this library https://github.com/hliberacki/cpp-member-accessor that uses a loophole in the C++ standard which allows one to access private members and methods in classes in external libraries that are not under the control of the library author. Since the loophole is legal, it works with all major compilers and on all platforms. No special compiler flags required nor illegal macros like #define private public. I think this should be integrated in Boost, is there interest other from myself? Before you say it is evil, consider all the good that can be done with this in responsible hands. You can add serialisation support to classes that you do not control and you can write efficient Python bindings. I have used this library now in three projects. I used it to add serialisation support and to provide memory views of C++ structures in Python (via the Numpy module), both wouldn't have been possible to do or not would not have been efficient without this. It is a single-header library with 85 lines of code, some of which are comments. This seems a bit small for a separate library, but I am not sure where it would fit in. Best regards, Hans

3 4