WriteString bug???

BlitzPlus Forums/BlitzPlus Programming/WriteString bug???

The Forum Archive is locked. These are the original blitzbasic.com forums, kept so their posts can still be read and searched. No new topics, replies or edits can be made here. To join the conversation, head over to the Blitz3D+ forums.

I know, I can write my own string write/read functions.

And I know that 2 bytes isn't the end of the world.

But why didn't anyone deciding the format of a string stored in this way (as opposed to null-terminated) do it with a byte for the number of bytes for the length? In 90% of cases it would save 2 bytes per string. It's not much, but it's still a fairly obvious way to do it, and if it saves space, why not?