Releases: bkrug/TI-string-buffer
Releases · bkrug/TI-string-buffer
v1.4.0
- This current version only reserves the amount of space for a new block that the caller requested. Previous versions would reserve twice as much space as the caller asked for. It was assumed that this would reduce the likelihood that blocks would need to move around within RAM very often when they would grow. But the resulting potential size of documents in RAM was disappointing. When using the TI-string-buffer library from https://github.com/bkrug/Emu-Writer, changing the library in this way does not appear to hurt performance.
- Fixed a bug in that occurred when the 16-bit word directly following the end of the memory buffer looked like the header for an open block.
v1.3.0
- When an out-of-memory or index-out-of-range error occurs, the routines now set the caller's EQ status bit to true. The caller no longer needs to compare the output in R0 to >FFFF or >FFFE to detect an error.
- Releases now contain two versions of the object code, besides the disk image.
- .OBJ contains TI-Files headers so that they can be read from an emulator that uses the Files-In-A-Directory approach to emulating disks.
- .NOHEADER.OBJ files do not contain TI-Files headers, and can be used from a Windows or Linux assembler like XDT99.
- The first word of an object file is no longer a value that came from a REF statement. Linkers for a TI-99/4a are likely to be confused when first word of an object file is neither a literal nor a label that comes from the same file.
v1.2.0
v.1.1.0
v.1.0.0
Introduces routines to
- designate an area of RAM as a chunk buffer.
- reserve a chunk within the buffer for a memory stream or test string of a certain length.
- free up a previously reserved memory chunk.
Also introduces array routines
- Initialize an array within a previously initialized buffer.
- Insert new elements into the array
- Remove elements from an array
- Get the memory address of a particular element in an array