|Luis Machuca Bezzaza d42218f65a New version 4||1 year ago|
|LICENSE||1 year ago|
|README.md||1 year ago|
|std.stcgafpmufdcppp.cpp.tags||1 year ago|
.tags file for the
Standard Templated Containers, Generic Algorithms, Functional Programming and Miscellaneous Utilities Framework for the Development of C-Plus-Plus Programs.
The Standard Templated Containers, Generic Algorithms, Functional Programming and Miscellaneous Utilities Framework for the Development of C-Plus-Plus Programs.
...Perhaps some explaining is in order.
There is a large set of utilities provided by the C++ Standard. These go from generic algorithms such as
find, to generic-use containers such as
list, to functionoid binders for purposes of functional programming such as
cref, and beyond.
Over time, there have been internet wars over what to call this set of standard utilities. Some people call them the "stdlib", some other people call them the "STL", with a defined meaning, and some other people also call them the "STL" but refer to a basis provided by SGI, and yet some other people talk about the "Standard STL" (more or less in the same vein as the ATM Machines in which you insert a PIN Number).
There was a small, in-joke contest in the Freenode
#C++ Channel (link to be provided)
to produce the longest, unambiguous term to refer to this set of utilities,
during which I came up with the acronym
STCGAFPMUFDCPPP, which I've adopted in all my code and documentation ever since (but I don't have much hope of it ever catching up).
As such, when I decided to create a tags file for this set of utilities, of course I ended up using this name for them.
Because Geany lacks one, and coming up with a sensible one is hard to do, and having a handy reference of the features the C++ Standard provides is always good, considering the language is evolving with a new Standard being released in 2011, another one in 2014 and then another one in 2017.
Just like any other
.tags file for Geany.
Just copy this into your config directory's
Like, right now. Just clone the repo (or extract this same tags file from the official Geany Wiki).
Function signatures of a number of template utilities, algorithms, etc., are provided. Because Geany lacks tag completion support from
<, constructors for features such as Standard containers can not be provided currently; they are included in the file only for completeness.
Several public function interfaces from the following C++ headers are provided in the tags file:
<algorithm>- generic algorithms to
findelements, perform transformations,
<functional>- reference wrappers,
functionobject and functionoid binders such as
<iomanip>- the various stream state functions.
<iterator>- the iterator helper conveniences such as
prev, as well as the upcoming C++14 and C++17 additions such as "global"
make_uniqueconveniences and various memory management related utilities.
<numeric>- the numeric utilities starting with C++11's
<system_error>- the functions used to tag error code and error category elements.
make_tupleconvenience and other tuple-related functions.
<utility>- the standard utilities such as
move, as well as some later additions.
clampand shift (left, right) algorithms from C++17 and C++20.
(, not on
<cmath>and other related headers.
<optional>(from C++ C++17).
''You might not have
#included the necessary header''.
Consult a C++ reference to determine what header you need to include to have access to these features.
''Your compiler might not have access to the C++ Standard required for those feayures''.
In the general sense, it's most likely you are using a compiler with an old (or new) enough C++ Standard that some of these features are not available or have changed in form, for example:
previterator utilities are provided.
unique_ptrfeatures are not provided.
<system_error>is not provided.
<algorithm>changed their return types from C++03.
<algorithm>are missing overloads.
<optional>are not provided.
<type_traits>are deprecated or removed.
<functional>are deprecated or removed.
Check your compiler and STL's documentation for information on what features you do actually have available.
If the case is that you are missing out on some features, you can still get some of them by adding to your environment / project a framework or toolkit library that provides a compatibility access layer for later C++ Standards. Examples include cxxomfort or Boost.