Hi there everyone. I'm working on a project right now, Base 671, in Axe, that will eventually run as an App, because it's gotten too big. I was using CrabCake so it would run at all, and the executable was nearing 1100 bytes, which is about how big all the billions of source files put together are, so I was running out of memory, so now it's going to be an app.

What do I need to change from a nostub ASM program when recompiling as an App? I know enough not to try and use SMC, but I'm not sure what all that entails. Could someone please provide me with a list of what I need to change/prevent from happening in an App's source code?

Also, if you access nibble data from your app, you'll need to use the alternate nibble read/write functions.

alberthrocks: That is because you're trying to write data back to Str1, which is a part of the application. As I explained in my previous post, that isn't possible. You should instead write the data to RAM somewhere, in scratch RAM or in an appvar.

How did we get on the topic of #Realloc()? That has to do with changing where in memory the A-θ variables reference, not strings or MemKit. I meant you should use a different pointer argument for Print() that will result in the string being copied to RAM, since Str1 is a part of your application and cannot be written to. For example: Print(L₁).

Regarding appvars, unless you want data to persist between runs (like settings or high scores), I would try to use scratch RAM to hold your data whenever possible. As far as I know, you don't need this string to persist between runs and it's pretty small, at most 9 bytes, so it's probably easiest to use scratch RAM to hold it.

Quote from: calc84maniac on September 22, 2011, 05:23:10 pm

Also, if you access nibble data from your app, you'll need to use the alternate nibble read/write functions.

What functions?

nib{nibble_address}^r and value->nib{nibble_address}^r

Quote from: buttsfredkin on September 22, 2011, 09:13:23 pm

Quote from: calc84maniac on September 22, 2011, 05:23:10 pm

Also, if you access nibble data from your app, you'll need to use the alternate nibble read/write functions.

What functions?

nib{nibble_address}^r and value->nib{nibble_address}^r

Um, you can't write a nibble to an App, can you?  Isn't it in ROM?

How did we get on the topic of #Realloc()? That has to do with changing where in memory the A-θ variables reference, not strings or MemKit. I meant you should use a different pointer argument for Print() that will result in the string being copied to RAM, since Str1 is a part of your application and cannot be written to. For example: Print(L₁).

Regarding appvars, unless you want data to persist between runs (like settings or high scores), I would try to use scratch RAM to hold your data whenever possible. As far as I know, you don't need this string to persist between runs and it's pretty small, at most 9 bytes, so it's probably easiest to use scratch RAM to hold it.

Oh... I was under the assumption that #Realloc() would cause the variables to be located in L₁ for modification.
So wait, if I do use Print(L₁), will I still be able to use regular variables?

(Or maybe I just don't get where the variables are/how do variables work/etc. )

Quote from: buttsfredkin on September 22, 2011, 10:33:33 pm

No, but if you have an appvar or some free ram, you can write nibbles to there. Correct, calc84/runer112/anyone else?

Yes, but you'd use the normal nibble commands for that.

Oh, ok. Got it.