Release notes for libmawk 0.9.5

This release has three main objectives:
 - proceed with porting - make sure libmawk compiles on more systems
 - implement binary save/load of the bytecode
 - revise memory handling, introduce limitation of memory allocation

Binary save/load is not about saving disk space: the binary version
is usually bigger than the script. Instead, among with the optional
limit on memory allocation, it is the first steps of a
larger plan, that involves:
 1. split the library in three parts: compiler, execute and common
 2. account and optionally limit resorce usage (memory, cpu)
 3. I/O hooks to control what files/processes a script may access/run

By the end of this road, libmawk will be safe to use in critical
applications because of 2. and 3. It will also be suitable for
embedded systems and other special applications if the large
parser/compiler does not need to be embedded all the time.

Unfortunately the binary save/load function works only on 32
bit systems at the moment but that will be fixed by the next release.