17.4.99
Version 1.0

18.4.99
V 1.01
- Fixed a stupid bug: parameters in multiple commands had an '\1' at it's end
V 1.02
- A second bug fixed; Applications couldn't send themselves GEMScript messages

19.4.99
V 1.10
- Fixed the wrong detection of empty arguments in test program
- Fixed bug: in a GS_REQUEST a wrong pointer to gs_info was sent.
- Fixed bug: return strings are returned as ASCIIZZ strings now.
- The interface has changed! The parameters in GEMScript commands are now
  to be handed over in the standard GEMScript notation; ASCIIZZ strings
  with empty parameters marked as an "\1". Because of this, several
  functions for the handling of ASCIIZZ strings are implemented in
  the hitrix library now.
  The second change is, that the remote application's return strings
  are now returned as a pointer to a copy of these strings. In earlier versions
  there could be a string overflow, when the app's return string was too long;
  Now the copy has always the right size.
  This copy is valid until the next sending of a GEMScript command;
  so if you need this return string for longer time, be sure that
  you copy or duplicate this return string!
  Several new functions for the handling of ASCIIZZ strings are
  implemented in the HITRIX.LIB because of this.

28.4.99
V. 1.11
- Fixed bug: The size of the global buffer in Gsc_command() and 
  Gsc_xcommand()was calculated wrong (strlen() instead of the length of the 
  asciizz string).Thus, a "System berschrieben" error could occur.
- Fixed bug: when an error occurred in Gsc_command() or Gsc_xcommand() during
  the beginning of the communication / GS_REQUEST (e.g. timeout, because
  the remote application doesn't understand GEMScript), an undefined return
  code was returned by Gsc_command()/Gsc_xcommand(). 
