Build
Configuration
Comments on the
individual components
Configuration
Options
An Evaluation of the
Benchmark Results of Hashcodes| Français Deutsch | Home Articles Links Résumé |
|---|
The code can be directly browsed here, or can be downloaded in on go in a tarred, bzip2'ed file. The license corresponds to the BSD license.
The code here was developed over a period of more than fifteen years; some of it was originally written in C, before I even started using C++. It has only been sporadically updated, according to the time available and my immediate needs. As such, it is in the state it is in; I do not claim that all of it is of acceptable quality for professional use. In fact, the quality varies greatly between components; I use some of the components more often than others, and these components are better maintained.
The current state of the code is somewhat transitional. Historically, my libraries supplied most of the basic classes I needed, things like String or ArrayOf. In practice, I've already replaced many of these classes with those in the standard, and long term, my guiding principle is that nothing that I maintain should do double duty with the standard library or Boost. For the moment, there are still some notable exceptions, especially with regards to Boost, either because I still have to support compilers which don't support Boost (Sun CC 5.5, in particular), or because I just haven't gotten around to rewriting the higher level code which uses them.
Likewise, there are no guarantees with regards to threading. In fact, most of the components are probably thread neutral---they don't use any static data nor other resources which might be shared, and so automatically offer the same guarantee as the SGI implementation of the STL (which is the only useful guarantee). Never the less, I've not yet done the analysis necessary to specify exactly which ones these are. (There is one exception: each time a singleton is used, I've arranged to ensure that it is initialized during static initialization---presumably before entering main, at least if the object is statically linked.)
There are several pages of documentation in the library itself, either in HTML or as plain text (not always in English, I'm afraid):
Build
Configuration
Comments on the
individual components
Configuration
Options
An Evaluation of the
Benchmark Results of HashcodesThere are man-pages for the executables which are actually useful, in HTML format:
Each sub-system in the library is also documented:
With regards to portability, all of the code here has been tested with the following configurations:
i80x86/linux/gcc:sparc/solaris/suncc:sparcv9/solaris/suncc:sparc/solaris/gcc:x86_64/linux/gcc:i80x86/win32/vc80: