HLA Standard Library / News: Recent posts

Added tarball of v3.1 source to the "View All Files" download page.

Added tarballs of the source in 'v4.0' and 'trunk' directories to the download page.

Branched off v4.0 of the HLA stdlib. Also renamed the "working" directory to "trunk" in order to match the SVN documentation and SVN common usage.

Fixed the pat.onePat, pat.oneOrMorePat, pat.zeroOrOnePat, and pat.zeroOrMorePat macros (they were completely broken before).

Finally finished the strings module documentation and posted several new str.catbuf* functions. This update becomes the stdlib v3.1 release.

Documentation for the new filesys file/pathname string functions was added to the system and lots of little defects in those functions were corrected.

Renamed a large number of the sourcefiles in the library so that the prefix of the filename matches the module to which it belongs. This helps reduce "namespace pollution" in the library file created when linking all the modules together into the library.

Sevag's string functions were added to the source code base. I also took the liberty of breaking up the source files into individual function files and filled in a few missing routines. Still have to include the test files he wrote, write additional test files, and write the documentation for all the routines.

The functions in the Bits, Chars, and Cset modules have been renamed to following the new naming conventions (i.e., they have "bit_", "ch_", and "cs_" filename prefixes).

The string functions were just renamed with a "str_" prefix. This is to make the library function naming more consistent and eliminate some problems having to do with two object modules in the library having the same name (a no-no for the linker).

Quick note to everyone -- the strings module documentation describes stdlib v1.x, not v3.0. This will be updated at one point or another. In the meantime, verify all string function prototypes by looking at the include/strings.hhf header file.

I've just uploaded the HLA v3.0 source code to the source forge repository. It's kept under Subversion source control. I recommend the Tortoise SVN client under Win32.