When it comes to the C64/C128 target, XCB3.1 allocates a total of 25 bytes for the following features:
1 byte for the error number (used for the error handling) - this was already in place in XCB3.0;
5 bytes for sound handling;
19 bytes for sprite handling.
But no matter if the program does or does not use some or any of those features, those bytes are always allocated in the compiled program and in RAM, and can't be used for variables, arrays or included binaries. They're potentially wasted bytes.
I'll also verify if a similar byte wastage occurs for the other supported platforms.
One temporary workaround to this is commenting out unused features in the lib/xcb3lib.asm file. One has to remember, though, to uncomment them once those features are needed in some other project.
As for the ERRNO byte, I propose moving this part in the lib/io/_error.asm file
When it comes to the C64/C128 target, XCB3.1 allocates a total of 25 bytes for the following features:
But no matter if the program does or does not use some or any of those features, those bytes are always allocated in the compiled program and in RAM, and can't be used for variables, arrays or included binaries. They're potentially wasted bytes.
I'll also verify if a similar byte wastage occurs for the other supported platforms.
One temporary workaround to this is commenting out unused features in the
lib/xcb3lib.asm
file. One has to remember, though, to uncomment them once those features are needed in some other project.As for the ERRNO byte, I propose moving this part in the
lib/io/_error.asm
filejust under
but I haven't tested it yet.