Artifact 126772eb72283fcea26bc4c6469adf593f3ccc036b020688c5ab804f5e56fb90:

Wiki page [Cxxomfort] by luismachuca 2019-01-01 15:01:45.
D 2019-01-01T15:01:45.081
L Cxxomfort
P 1199f342f9e0ad9532438e691e98c7a75d8986d97f087de97a2b2a173246efc9
U luismachuca
W 3977
<blockquote style="font-size:85%;"><b>Comfort</b>, n. <nowiki>[3]</nowiki>

A consolation; something relieving [https://en.wiktionary.org/wiki/suffering#Noun|suffering] or [https://en.wiktionary.org/wiki/worry#Noun|worry]. 

"We still have the spare tire? That's a <b>comfort</b> at least."

([https://en.wiktionary.org/wiki/comfort#Noun|Wiktionary])
</blockquote>

<em>Cxxomfort</em> (<small>cxx as in C++, comfort as in comfort</small>) is a small, header-only library that backports some of the nifty goodies from the more recent C++ Standards to previous versions such as C++03 or C++11: <tt>nullptr</tt>, <tt>begin/end</tt>, <tt>type_index</tt>, <tt>byte</tt> or the newer algorithms and functors, as well as many others, are made available.

I wrote it originally to facilitate my working with the evolving C++ standard as I was getting back into the language. It is intended to reduce the amount and stress of code rewrite while at the same time assisting in backwards and forwards portability.

Current version: 20181111 (.80)

<table border="1"><tr>
<th>Quickie Links</th><td>[#qad|Quick&Dirty Install and Use] </td><td> [Features]  </td><td> [https://notabug.org/lmachucabezzaza/cxxomfort-examples|Examples (external)] </td><td> [/ticket|Issues] </td>
</tr></table>

<a id="qad"></a>
<h2>Quick & Dirty</h2>

<b>Installation:</b>

<verbatim>
fossil clone http://ryan.gulix.cl/fossil.cgi/cxxomfort cxxomfort.fossil
fossil open cxxomfort.fossil
</verbatim>

<b>Usage:</b>

Using this library is as simple as writing C++ code. Include the cxxomfort header in your code:

<verbatim>
#include <cxxomfort/cxxomfort.hpp>
// or #include <cxxomfort/base.hpp> if you only plan to use the basic features
</verbatim>

<verbatim>
# compile with:
(compiler_options...) -I /path/to/cxxomfort ...
</verbatim>


<h2>Project Documentation</h2>

<ul>
<li>[Installation]</li>
<li>[Configuration]</li>
<li>[http://ryan.gulix.cl/cxxomfort-docs/html/index.html|Autogenerated Documentation]</li>
</ul>

You can include only <code>cxxomfort/base.hpp</code> in library code if you only need the <b>base subset of cxxomfort features</b>, without TR1-related utilities or any other sort of advanced features. [Features] for more information.

<ul>
<li>[BehaviourMacros]</li>
<li><b>[Features]</b> - what is backported or implemented from various C++ Standards
<li><b>[Supplements]</b> specific to cxxomfort, such as extra algorithms, foreach loops, local function emulation, fixed_vector, etc... </li>
<li>[Extras] that don't take part of the default distribution, such as implementation of simple ranges, etc...</li>
<li>[Transparent Headers]</li>
</ul>

Frequently asked questions? [FAQ].

Looking for usage examples? https://notabug.org/lmachucabezzaza/cxxomfort-examples

<h2>Meta</h2>

The purpose of this library is to ease writing natural-feeling, forwards-compatible code <i>once</i>. As such, some design decisions are made that might conflict with conflict with certain pedantic "coding styles". For a quick, uncomprehensive check read [Rationale], and also take a look at [https://softwareengineering.stackexchange.com/questions/142836/achieving-forward-compatibility-with-c11] for evolution of the rationale.

The library does not aim to be perfect - that way lies madness, suffering, and suffering leads to anger, and anger leads to overused lines from movies. Instead, it aims to be "good enough" for the backports to be usable as far back as possible Standards-wise - all while remaining relatively simple.

For a list features included in this library and what are the Standard Proposals they come from check [Implementation Status].

Credits to the various solutions in [Credits].

License information in the included <code>[LICENSE.txt]</code> file.

<small>Q&A / reports at <code><nowiki>luis[dot]machuca[at]gmail[dot]com</nowiki></code> or file a request in the [/ticket|ticket system].</small>


Z 381f3da8f634498f0bcd07e688a4ac89