This is a BETA release.

This tutorial is almost done. All I have left to do is the optimization, debugging, then the stages of release. Please remember as you read this:

1. My knowledge on the topic is not perfect. Its possible I may have left stuff out (in fact, I'm sure I did). This has been a learning experience for me, as well as an attempt to speak. So, please be nice. This is a beta version.

2. Feel free to edit/remove/add stuff as you feel necessary. Just, please make your changes in a different color than the rest of the text, so I can distinguish them.

Thanks

Please ignore the formatting. It should be pretty readable in .txt.

cool, I'll check when I have some more time in the middle of the week. Feel free to poke me again if I forget

give me a little time, i'm reading it now.

Err, this might sound kind of bad, but...

This is very dangerous. There are no errors produced.

Not true.  It is not very dangerous if you know what you are doing, and errors *are* produced.

The RAM is relatively unorganized and unprotected.

Not true.  It is quite organized.

A fixed part of the calculatorÕs RAM cannot be edited, used or modified.

Yes it can, it's just dangerous.

-TI-84

There is no such thing.

a program designed for use on a TI-83 Plus will not work on a TI-83 or lower

Yes it can.

I don't mean to nitpick, but I'm trying to help you make a good tutorial.

Well, there are a few specific tokens to each calc, but most programs can be transferred between any z80 calculator.

There are many differences between the 83 and 83+, but most basic programs will work on each.

I am starting to read in a minute. So far, though, I noticed something:  Your ' characters show up as Õ. For example calculatorÕs.

This may be because I started in Word and then converted into .rtf. I'll look into it.

Err, this might sound kind of bad, but...

Quote from: ACaglino

This is very dangerous. There are no errors produced.

Not true.  It is not very dangerous if you know what you are doing, and errors *are* produced.


I'll make that clarification, thanks.

Quote from: ACaglino

The RAM is relatively unorganized and unprotected.

Not true.  It is quite organized.


Do you have any sources that can help me explain its memory structure?

Quote from: ACaglino

A fixed part of the calculatorÕs RAM cannot be edited, used or modified.

Yes it can, it's just dangerous.


*In TI-Basic, it can't. I'll clarify, though.

Quote from: ACaglino

-TI-84

There is no such thing.


Ok.

Quote from: ACaglino

a program designed for use on a TI-83 Plus will not work on a TI-83 or lower

Yes it can.


I'll switch that to: "While some programs written for the TI-83 Plus will run on a TI-83 or lower, there are just as many that experience compatibility issues." How's that?


I don't mean to nitpick, but I'm trying to help you make a good tutorial.

I welcome it. Keep 'em coming.

Actually, I think the only way to really damage your calc with assembly is if you unlock flash and do a bad manipulation.

I'm not going to delve that deep into it.


Also you might want to specify that the total calc RAM is 32 KB and that the use can only use 24 of it. Right now it seems a bit like you say the entire RAM totals 24 KB.

Is there some sort of "map" of the memory I can enclose?

Ok, got more time to read now. On chapter 3, now.

For planning, I would add a note that if someone is new to the language or never coded a game before, he should start small. Starting too huge without making sure if you can do a project and if it's feasible at all can discourage you.

I'll mention that.


I would also give some references to memory leaks in the Lbl/Goto part, warning people that misuse of them can cause errors when the program is running for a while (and slow down).

Can you elaborate a little?

Edit: Also, as a side note, if I have left out any important topics or you want to add something to it, please either post here or email to me at [email protected]. I'm pretty sure I've missed at least one major topic.

Ahh, you mean like the "self replicating code" type of scenario (I use "self-replicating" in the loosest possible manner)?