| version 1.3, 2002/12/24 16:49:56 |
version 1.4, 2003/08/09 23:58:13 |
|
|
| <!-- $Platon: libcfg+/doc/sgml/preface.sgml,v 1.2 2002/10/07 10:54:40 rajo Exp $ --> |
<!-- $Platon: libcfg+/doc/sgml/preface.sgml,v 1.3 2002/12/24 16:49:56 nepto Exp $ --> |
| |
|
| <preface id="preface"><title id="preface.title">Preface</title> |
<preface id="preface"><title id="preface.title">Preface</title> |
| |
|
| <para> |
<para> |
| |
|
| While developing lot of C/C++ applications we often comes to state, that we |
During our daily involvement in C/C++ development, we were often confronted |
| need sophisticated command line and configuration file parsing library. We also |
with such repetitive and mechanical tasks as parsing the command line or |
| knew already existing parsing libraries for both, command line and |
configuration files. We quickly came to the realization that a robust and |
| configuration file, such as <productname>popt</productname> or |
versatile library for performing those tasks could save a substantial amount |
| <productname>parsecfg</productname>, but these libraries can work only with one |
of our development time. Examples of existing tools with similar |
| from the issues. We wanted one library for whole configuration stuff. We wanted |
functionality included <productname>popt</productname> or |
| also to share configuration properties in one data structure, we wanted to |
<productname>parsecfg</productname>. Although both were effective at |
| parse both configuration resources in similar way with huge set of features. So |
addressing one of the aforementioned problems, neither one provided a unified |
| the &name; was born... |
solution. Clearly, the stage was set for a new tool with a uniform and |
| |
consistent API for parsing both the command line and configuration files. And |
| |
that is how &name; was born... |
| |
|
| </para> |
</para> |
| </preface> |
</preface> |