I have no dedicated use for it now, I do it more for the fun and out of interest. In most of the cases, a static memory model is sufficent, but dynamic allocation can simplify some things, for example when working with files/file systems (I have something in mind where I could need it)
It's a good idea to map the RAM with an array over the whole space and working with overlays, but here you also may want to know how much space there is if you don't want the internal variables running into the frame space.
_strbuf is located at the beginning of the frame space (first 24 bytes are Bascom's global string buffer), that's the address the constant _gstrbuf is pointing to.
Thank you for your input, my solution now is a compromise, I still use the dummy variable and an offset which I have to look after in the report. That way I just have to adjust things if Bascom's internal variable usage changes. I think that's the most convenient way possible...
Best regards
↧