This is NOT a thread-safe library. There are numerous places where race conditions and other nasties can rear their ugly heads. If you write a multi-threaded application that uses libdoomwad, restrict its use to a single thread and it might be okay.
libdoomwad uses new/delete for memory. I did not override either operator, nor did I use specialized memory pooling for optimization. It relies on the STL Container library in several places, so the underlying implementation may add something to the equation.
Porting to another platform should be fairly easy. The vast majority of libdoomwad's code is platform-indpendent. Endianness should be the only issue, but hopefully I put endian handling code everywhere it needs to be.
Generated on Fri Jun 10 19:38:51 2005 for libdoomwad by
1.4.0