30796e5729
ircd::json::tuple: Fix template name related for clang-11. ircd::ctx: Fix template related for clang-11; inline linkages. ircd:Ⓜ️🪝 Fix template related for clang-11. |
||
|---|---|---|
| .. | ||
| buffer.h | ||
| buffer_base.h | ||
| const_buffer.h | ||
| copy.h | ||
| fixed_buffer.h | ||
| move.h | ||
| mutable_buffer.h | ||
| parse_buffer.h | ||
| README.md | ||
| shared_buffer.h | ||
| unique_buffer.h | ||
| window_buffer.h | ||
Memory Buffer Tools
This is a modernization of the (char *buf, size_t buf_sz) pattern used
when working with segments of RAMs. While in C99 it is possible (and
recommended) for a project to create a struct buffer { char *ptr; size_t size; };
and then manually perform object semantics buffer_copy(dst, src);
buffer_move(dst, src)``buffer_free(buf); etc, we create those devices using
C++ language features here instead.
This suite is born out of (though not directly based on) the boost::asio buffer
objects boost::asio::const_buffer and boost::asio::mutable_buffer and the
two principal objects used ubiquitously throughout IRCd share the same names
and general properties. We also offer conversions between them for developers
working with any asio interfaces directly.
To summarize some basics about these tools:
-
Most of these interfaces are "thin" and don't own their underlying data, nor will they copy their underlying data even if their instance itself is copied.
-
We work with signed
char *(andconst char *) types. We do not work withvoidpointers because size integers always represent a count of single bytes and there is no reason to lose or confuse that information. Ifunsigned char *types are required by some library function an explicit cast touint8_t *may be required especially to avoid warnings. Note that we compile this project with-fsigned-charand don't support platforms that have incompatible conversions.