Joined: 16/09/2019 Location: United KingdomPosts: 4092
Posted: 04:25pm 03 Mar 2022
Because it would change the line numbers and mess up any carefully setup pointers from your original example.
I agree, let's have:
BINARY name 01234567 89ABCDE ... END BINARY
Though due to MMBasic limitations BINARY and CSUB would probably end up having to share a command token so basically you're back to using the CSUB mechanism with some syntactic sugar.
My real issue is that we had something with all the power required and so far we're looking at replacing it with something less capable.
It's not where to store the data in memory that is the problem, it's where to read the data you want to store in memory from, or to put it another way how to initialise the memory storage.
If I wanted to use files I could just use binary files, they wouldn't have to be bitmaps. Also locating files relative to a .INC file is problematic since once a program is running MMBasic doesn't know anything about the arrangement of the .INC files that made up any given program.
But it does pose the question without the CSUB mechanism how do you put bitmaps into programs on 'mites that don't have an SD card reader ?