jarro2783/cxxopts VS text

The most feature-rich C++ CLI library is CLI11. Other popular choices include Boost.ProgramOptions, argparse, cxxopts and others.

I've used cxxopts and can't complain. It's available on both Conan and vcpkg.

For streamlined command line option parsing check out a library like cxxopts or similar. There are plenty out there.

Have a look at cxxopts which is similar to the python getopt functions, It's header only so easy to use (just dump the header in your project). There is also boost::program_options but this requires boost which is big.

I use CLI11 for more complex things, https://github.com/jarro2783/cxxopts for simpler interfaces, and boost.program_options if I have to and have boost anyways as dependency.

Let the user pass the path/filename as an input argument to the program. Your main() function takes arguments from the console, so you could invoke your program as .\my_program --err_log "\path\to\my_errors.log". Of course this again only works if executed from the console - you can however create a desktop shortcut that invokes your program with this argument and you can also configure your IDE to pass this argument when running your program. To make parsing input arguments easier, use a library such as cxxopts

You probably want the header only library cxxopts.

To make parsing command line options easier I can recommend the cxxopts library.

I have previously used this: https://github.com/jarro2783/cxxopts

It sounds like a generic length function in Unicode in 2023 is no longer a good idea. These articles complaining about the variety of lengths in Unicode are annoying at this point. Pretty much all of them can be summed up as, "Well, it depends." And, that isn't wrong. But nerds love to argue until they are blue in the face about the One Correct Answer. Sheesh.

This is the most interesting comparison article I have seen in years about Unicode processing in C++: https://thephd.dev/the-c-c++-rust-string-text-encoding-api-l...

The author is also the lead on an open source C++ Unicode library called ztd.txt: https://github.com/soasis/text

How does this compare with https://github.com/tzlaine/text and https://github.com/soasis/text ?

You might consider https://github.com/soasis/text (https://ztdtext.readthedocs.io/en/latest/index.html) which is a proof of concept of this proposal that we may get in C++26

from this link for the tested option that was the only one to check all the boxes green in the article... it makes me ask myself if the article was written biased with the purpose of promoting ztd.text and that these boxes/criteria were to an extent cherry-picked with that purpose in mind.

Github: https://github.com/soasis/text

That's a huge misrepresentation of the reality. Of course it has its own string class, because there has not been a proper type in the standard library for Unicode text, and for many, we are not there yet (otherwise we would not be having other libraries filling the empty space).

You can checkout ztd.text, which implements presented ideas. Few years passed, so they were more polished too.

The library you talk about is https://github.com/soasis/text and he has an account here.

Project Link: https://github.com/soasis/text Announcement/Blog Link: https://thephd.dev/any-encoding-ever-ztd-text-unicode-cpp

PS: found some example code in the github project which seems to take care of the special Windows situation:

https://github.com/soasis/text/blob/main/examples/documentat...

Unfortunately this doesn't look so simple anymore.