No writeable memory at this address

Need I say more???

I know that you can get a module to sort this out, but surely time to do it properly?

And while we’re here, could the BASIC module extend it’s workspace when (e.g.) a DIM doesn’t fit?

Yes!
For ARM7 often a higher wimpslot fix this.

could the BASIC module extend it’s workspace when (e.g.) a DIM doesn’t fit?

Yes. The pseudo-variable END= sets the end of the wimp slot, and can be used to make more space in the user memory, from where DIM creates its block. This might be used like this:

It is usually better to set a sufficiently large wimp slot in an application !Run file, or, if you are running a non-wimp BASIC program, set the Next slot in the Task manager to a higher value.

If you are completely unable to predict the size of the DIM there are other options, among which is my Basalt BASIC extension module. Then you can DIM away merrily and the wimp slot is changed without any other action; you can change the size of DIMmed blocks, too.

I know that you can get a module to sort this out, but surely time to do it properly?

Yes. Integrating Absolutely with the OS has been on my todo list for some time, since I’m not in the middle of anything at the moment I’ll see if I can get it done in the next day or two.

could the BASIC module extend it’s workspace when (e.g.) a DIM doesn’t fit?

Not automatically, no, as you may have extended the WimpSlot yourself and have your data in there after the end of BASIC’s memory. As described, you can do it manually (if you know what you’re doing), or you can use something like Basalt that can do it automatically (AIUI).

The latest ROMs now have Absolutely’s functionality integrated into the OS. Let me know if you run into any issues.

I look forward to hearing that there is a Pi patch/release/update/whatever for this!

If you’re happy with using a development ROM image then you can just grab the latest one from the downloads page