EDIT: Also, because I'm sure I'm not the only one wondering about this, I'll go ahead and ask it:

Quote from: SirCmpwn on March 12, 2011, 08:10:56 pm

Nested libraries would be nice.

Nested libraries?

He means libraries within libraries. Remember that in Axe, you can use prgmNAME to include the Axe program called NAME as if it were inline. Nested libraries means that we could use this same concept within the referenced program (which we currently can't do).

EDIT: I realize that my sudden little OOP tutorial might have blown you guys away just a bit, seeing as no one has posted to this forum since I posted. I rewrote it a little bit.

Oh, an OOP thread! My base is in C#, which is an incredibly OOP language. I would be happy to answer any questions about OOP that you guys might have. In the meantime, I can tell you guys what the basic idea of OOP is:

In low level programming, everything is managed by the programmer. All of the objects in the game, and all of their properties, are handled directly by the programmer. For example, to define a spaceship with an X, Y, and rotation in TI-BASIC, and then move it 10 pixels forward, you would do something like:
0->X:0->Y:0->R
X+sin(R)*10->X:Y+cos(R)*10->Y

However, in OOP, all of the objects in a program are encapsulated in classes. A class is basically an object's definition, which contains all of the properties of an object. For example, in C#, you would say
class Ship
{
public int x;
public int y;
public float rotation;
}
to define the class called Ship, with integers x and y and a floating point number "rotation". The keyword public is a special keyword that means that other objects can mess with this value.
Within that class, you can add methods and subroutines, which do things to the ship's variables. For example, you can define this method within the definition of the Ship class:
public void Move(float amount)
{
X += Cos(Rotation) * amount;
Y += Sin(Rotation) * amount;
}

Once you have defined your Ship class, you can create a new instance of it, just like you would any other variable type (e.g. an integer or float). Then, later in the program, you can access its variables and call its subroutines. To reference a part of a class, first type the name you gave that particular instance of the object, then a period, and then the property you want to reference.
Ship ship = new Ship();
ship.rotation = Pi;
ship.Move(10);
Print(ship.x);
This piece of code creates a new instance of Ship, sets its rotation to Pi, moves it forward 10 pixels, and prints the ship's x-coordinate (which should now be -10).

Now, you might be asking: Why would I ever want to use this? There are two main reasons you would.
First, while it might be easier to manage one ship in low level programming, how about managing 100 of them? To track down all 300 variables, even in a list, would be unbearable, especially if you decided later that ships also need to have health or something. However, if you create a list of Ships, you can manage each ship individually.
Second, objects encapsulate things that you just don't want to manage, or want to protect somehow. For example, our Ship had a subroutine called Move on it to move the ship forward. Instead of having to remember sines and cosines every time a person wanted to move the ship, they could just set the rotation and movement amount and just say "Move". OOP also lets you hide variables that an object needs to know about, but not the rest of the game.

And objects have real-life applications as well, more so than in games. For example, you might want to create an object called CALCnet that manages calculator linking. By using this object, you don't have to worry about all of the little details and issues with CALCnet. All you have to do is start it up, shut it down, and tell it to send frames to people.

So, that's OOP 101. There is still a LOT more to the world of OOP, and I would be happy to share my knowledge.

EDIT: I realize that the sheer magnitude of this explanation might have scared you guys away. I hope I can be clearer and help you learn OOP.

@Compynerd255 this limit applies to the executable, not the source.

Then how come 10K programs, such as FireTracks and Megaman, can exist?

Yes, since its hex code. It's compiled directly to Z80 instructions. Unless, of course, you don't need to flip the addresses to begin with.

You do have a good point, JustCause. Authors should warn their users of such content. However, different people have different standards, and what might be considered perfectly fine to one person might be appalling to another person. A rating system would standardize the opinion.
If we wanted to create a calc rating system, what we could do is when people review the game on Ticalc, Omnimaga, or any other rating site, they would also give the game content ratings based on several scales for individual pieces of content. Then, the game's calc rating would be the average of all of the ratings the game has gotten, weighted according to the rater's Respect level (e.g. a person who simply gives random values to the ratings without even playing would not have as much of an influence as a person who actually plays the game and gives honest ratings).

And yes, I didn't realize that palpable was the wrong word. A better word would be palatable.

This problem is really simple. I can't remember the exact code off the top of my head, but it goes something like this:

0->C
Disp "WAITING...",i,"PRESS ANY KEY",i,"TO CANCEL",i
Repeat C
 Get->A
 Send(100,1000
 !If A-100
  2->C
 End
 If getKey
  1->C
 End
End
!If C-1
Goto <FailLabel>
End
Disp "SUCCESS!"
Goto <PassLabel>

Similar code is in Eitrix, if you want to see it in action.

It's not a compile bug. I have to pull my source out of backup every time the interrupt function crashes, so I don't believe that's the problem. I would like to see what is going wrong. For now, however, I am calling the interrupt function several times in my main game loop as a workaround, and it seems to be working.