Artifact 6576f09652af5a3c46e702cfb7d355881f3aae91255f43fdf9683d695490364e:

Wiki page [Cxxomfort] by luismachuca 2019-02-16 01:08:26.
D 2019-02-16T01:08:26.630
L Cxxomfort
P 511ba92bd9c9347455475ade7fd30ede7d5822598aa9d05213e437969ea9faaa
U luismachuca
W 4121
<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 various facilities from more recent C++ Standards, providing access to them 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: 20190128 (.88)

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

On your shell:

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

On your code:

<verbatim>
#include <cxxomfort/cxxomfort.hpp>
</verbatim>

<h2>Project Documentation</h2>

<table border="1">
<tr><th class="header" style="width:35%; text-align:center; ">Install & Setup</th><th class="header" style="text-align:center;">Autogenerated Documentation</th></tr>
<tr><td style="vertical-align:top; padding-left: 0.2em;">
In the simplest form, installing the library is as simple as cloning the repo and adding the path to the compiler's <tt>#include</tt> search path.


<ul>
<li>[Installation]</li>
<li><em>[/download|Packaged versions]</em></li>
<li>[Configuration]</li>
<li>[Per-Compiler Notes]</li>
<li>[/uv/html/|Autogenerated Documentation][↗]</li>
<li>[/ticket|Issues / Ticketing System] </li>
<li><a href="https://notabug.org/lmachucabezzaza/cxxomfort-examples" target="_blank">Examples [↗]</a> </li>
<li><em>[FAQ]</em></li>
<li>[/doc/trunk/cxxomfort/LICENSE.txt|LICENSE]</li>
</ul>
</td>
<td style="vertical-align:top; padding-right:0.5em;">
Usage is as simple as including a header and start coding:
<verbatim>
#include <cxxomfort/backports.hpp> // for the backports
#include <cxxomfort/cxxomfort.hpp> // for the whole package
</verbatim>

<ul>
<li>[BehaviourMacros]</li>
<li><b>[Features]</b> - backports or emulations from various C++ Standards. </li>
<li><b>[Fixes]</b> - fixes to elements that are broken in <tt>std</tt> in certain compilers. </li>
<li><b>[Supplements]</b> - features and interfaces specific to cxxomfort, that complement the various C++ headers. </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>

</td>
</tr>
</table>

<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].

<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 e5d7f5295ce427a9fff6fb31a223fc07