*** empty log message ***

diff --git a/allParam/RELEASE_NOTES b/allParam/RELEASE_NOTES
new file mode 100644 (file)
index 0000000..10b8991
--- /dev/null
+++ b/allParam/RELEASE_NOTES
@@ -0,0 +1,60 @@
+Author:  Benjamin Sailer
+         TUM/E12
+         Benjamin.Sailer@ph.tum.de
+Version: 0.2
+Date:    2001-02-21
+
+allParam library Release Notes for Version 0.2
+==============================================
+
+Enhancements:
+-------------
+
+1. Common header file
+
+All libraries now use a common header file allParam.h, to be placed in
+$HOME/include or the system wide includepath (/usr/local/include). This
+requires a little change in the makefiles of programs using the libraries but
+at last ensures that only the linking has to be done when changing the
+parameter source (which was not the case in Version 0.1).
+
+2. Multiple setup support
+
+The support of multiple setups is introduced in Version 0.2 of the libraries.
+This is due to the fact, that different programs may need different setup
+parameters at a time, that all come from a single parameter server. The main
+change for the user results in a second constructor for the Param structure,
+handing over an additional setup string to distinguish the parameters.
+This constructor,
+> conSetupParam(Param *, const char *)
+is an alternative to the for compatibility reasons co-existing
+> conParam(Param *),
+that will be changed to the final
+> conParam(Param *, const char *)
+in one of the next releases. For libfileParam.a and libtclParam.a, the setup
+is translated to file names. See the READMEs of those particular libraries for
+details.
+
+3. Storage of parameters
+
+In the new allParam library Version a writeback of parameters (scalar integers
+and scalar strings) is introduced. They either fill files in tcl-syntax (for
+libfileParam.a and libtclParam.a) or fill a table in the database (in the
+case of liboraParam.a and libpsqlParam.a). Those stored parameters are
+available for Param_get-calls immediately afterwards. It is possible to write
+down the same parameters more than once which changes the value to the most
+recent one (or at least sould do that). Like parameters to read, parameters to
+write are identified by "setup", "name" and "idx".
+
+4. Test extension
+
+The test suite has been extended to proofe the new features.
+
+Bugfixes:
+---------
+
+libFileParam.a does not rely on strings without whitespaces anymore. The large
+fix amount of allocated memory at libfileParam.a has been changed to a
+dynamically allocated and relocated memory to reduce the consumption to the
+needed space and extinguish the magic number of maximal 1024 parameter entries.
+