μSF is a lean C++ string format library (mainly) for embedded platforms. Its main purpose is to be a small, safe and fast alternative to (s)(n)printf functions adding some additional features. The library is in its very early stages of development and its interface can (inevitably will) change at any time based on my own usage experience and any feedback / comments I get.
Damn... yet another formatting library??? Well, basically I have no sympathy for the (s)(n)printf functions, even less for the cumbersome IOStream's interface. I really love the {fmt} library but it has an hefty price tag when working with targets with only a few kB of flash and RAM available. This happens mostly because {fmt} has a lot of features (rarely needed in an embedded target) and also because it falls back to printf in some cases (hopefully this is still true in the latest version).
So, based on my love for the {fmt}'s format string syntax (itself similar to the one of str.format in Python), I decided to roll my own version with a nice balance in mind between code size, execution speed and available features that made sense to my main target platforms, small embedded micro-controllers, mostly ARM Cortex-M0/3/4.
I also did it for the challenge of making it and it turned out to be more demanding than I has expecting at first...
- Safe alternative to (s)(n)printf and IOStream functions.
- Doesn't allocate any dynamic memory.
- Ease of use: single header file library usf.hpp without any external dependencies.
- Small code size: both in terms of source code (around 2500 loc) and produced binary size.
- Reliable: it has an extensive set of unit tests (work in progress).
- Support for positional arguments.
- Support for user-defined custom types.
- Portable and consistent across platforms and compilers.
- Clean warning-free codebase even with aggressive warning levels.
- Support for C++11/14/17 standards:
- GCC 4.8.1 or greater
- Clang 3.4.0 or greater
- Should work with MSVC++ 14.0 or greater (untested yet)
- Complete unit tests.
- IAR and Arm Compiler 5/6 support.
- Dynamic width and precision support.
- Add a std::string replacement with inplace storage.
- Add more functions to usf::StringSpan and usf::StringView classes.
- Besides formatting, also printing capability with custom output handler, e.g.: Console, UARTs, LCDs, etc...
- Wide character strings support (the foundations are done but it was never used or tested).
- Better floating point conversion routines (the current ones suck!). Looking at the possibility of adapting ryu's algorithm.
(wip)
To get started with usflib all you need to do is download the latest version which is just a single header file and add it to your source files (or add this repository as a git submodule).
Assuming you can use the single header file directly: #include "usf.hpp" - place it either in the same folder of your source files or add its location to the include paths of your build system.
#include "usf.hpp"
/*...*/
char str[64]{};
usf::format_to(str, 64, "Hello, {}!", "world"); // str == "Hello, world!"
usf::format_to(str, 64, "dec:{0} hex:{0:x}", 16); // str == "dec:16 hex:10"
usf::format_to(str, 64, "{0}{1}{0}", "abra", "cad"); // str == "abracadabra"All functions and types provided by the μSF library reside in namespace usf and macros have prefix USF_.
The library API provides a few simple format functions and a minimal string view / string span like classes that offer an alternative to the standard ones.
The string view / string span types are template classes that accepts the type of character via a template parameter, having (for now) a char type specialization.
template <typename CharT>
class BasicStringView{ /*...*/ };
using StringView = BasicStringView<char>;
template <typename CharT>
class BasicStringSpan{ /*...*/ };
using StringSpan = BasicStringSpan<char>;Similarly, the format functions are template functions, allowing the use of different character types. Two sets are defined, a basic_format_to being the template version and another called format_to being the char type specialization.
The following format functions use the same format string syntax of {fmt}, which is itself similar to that of Pythons's str.format (although not every option is implemented).
The output format is specified in the str_fmt string/string view. It can contain literal text and replacement fields surrounded by braces {}. The fields are replaced with formatted arguments in the resulting string.
The objects to be formated are represented by the args argument list.
- Formats the args arguments, writes the result to the iterator (pointer) str and returns an iterator (pointer) past the end of the output range. The function fails if the resulting output string size is greater than str_count size.
template <typename CharT, typename... Args>
CharT* usf::basic_format_to(CharT* str, const std::ptrdiff_t str_count,
usf::BasicStringView<CharT> str_fmt, Args&&... args);
template <typename... Args>
char* usf::format_to(char* str, const std::ptrdiff_t str_count,
usf::StringView str_fmt, Args&&... args);- Formats the args arguments, writes the result to the string holded by the string span str (don't change the span range) and returns a new string span with the range adjusted to the output string size. The function fails if the resulting output string size is greater than str's span range.
template <typename CharT, typename... Args>
usf::BasicStringSpan<CharT> usf::basic_format_to(usf::BasicStringSpan<CharT> str,
usf::BasicStringView<CharT> str_fmt, Args&&... args);
template <typename... Args>
usf::StringSpan usf::format_to(usf::StringSpan str, usf::StringView str_fmt, Args&&... args);(wip)
(wip)
(wip)