The Metasilk Language / News: Recent posts

Seeing as the current SVN development is turning libmetasilk into an extendable markup language of sorts, it's no longer fitting to call this project The Metasilk Framework. So it's time for a name change. I hereby declare this project to be known as The Metasilk Language.

Spring time is finally showing it's self and I've already starting planing out the list of exciting new features for v0.1.1, so this implies it's time to release v0.1.0 as stable. Note, this is just a version bump from v0.1.0-pre3.

For v0.1.1 the way data is compiled and referenced within libmetasilk will be rewritten in order to allow for more complex features one would expect from any modern markup language. Such features on the block are nested metasilk objects, the use of C-like expressions for data, functions for manipulating metasilk data/atoms and user defined data-types/formats/functions.

libmetasilk-0.1.0-pre3 was released to fix bugs in string and hostname parsing, fixed a few potential buffer overflows and minor changes to Makefile.in.

libmetasilk-0.1.0-pre2 was released to fix bugs in the unification and compiling of metasilk_atom objects. Also the previously reported memory leak turned out to be a false-negative created by valgrind's misreading of bison generated parser code.

Well I decided to upload libmetasilk-0.1.0-pre1, despite there being one annoying memory leak left in it. Valgrind can't find where the leak is coming from, just that there's always one allocated chunk left over at exit time. All the basic features are present in this prerelease, but code is heavily undocumented. There are also some serious bugs that were just discovered in pre1, fixes are being quickly conjured up for pre2.