January 2023 - Boost-users - lists.preview.boost.org

boost::log - tmp output log with decorated name ?
by Nicholas Yue 26 Jan '23

26 Jan '23

Hi, I plan to use boost::log for my C++ application logging needs. Does boost log have a convenient function for generating decorated filename in /tmp ? Something along the line of <app_name>_<timestamp>_<process_id>_<thread_id>.log This allows me to accumulate logs between runs to capture and compare. Cheers -- Nicholas Yue https://www.linkedin.com/in/nicholasyue/

1 0

Fwd: [boost.interprocess] Are there pitfalls using managed_shared_memory?
by M L 10 Jan '23

10 Jan '23

Are there common pitfalls when using boost::interprocess::managed_shared_memory in order to share a variable in the following way (Cpp,Windows OS)? managed_shared_memory managed_shm(open_or_create, "my_shm", 1024); // Write int *i = managed_shm.construct<int>("Integer")(42); // Read std::pair<int*, std::size_t> p = managed_shm.find<int>("Integer"); - Is the shared memory deleted, when the application is stopped? - Do other programs or services can bear with this method without crashing? -is there a danger that shared memory could be accumulated with some kind of overflow? Question: what does one have to consider when using this method? Thanks for help.

1 0

ASIO openSSL 3 support
by Ofer Lent 03 Jan '23

03 Jan '23

Hi, https://www.boost.org/users/history/version_1_80_0.html, "Asio" section, states: "Fixed compatibility with OpenSSL 3.0.4 and later." However, API-s which were deprecated in openSSL 3 still exist in boost_1_80_0.tar.gz<https://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/boost_1_80…> --> boost/asio/ssl/impl/context.ipp: · RSA_free · DH_free · d2i_RSAPrivateKey_bio · PEM_read_bio_RSAPrivateKey · SSL_CTX_use_RSAPrivateKey · SSL_CTX_use_RSAPrivateKey_file · PEM_read_bio_DHparams Is there a plan to update them? BTW - It is possible to build an application with these deprecated API-s by using CFLAGS += -Wno-deprecated-declarations, but in my understanding it is not acceptable for FIPS compliance. Thanks! ------------------------------------------- This message is confidential. If you believe you received this message in error, please inform the sender and delete this message and all attachments.

2 1