ASM programs are, essentially, hex. though i just realized it won't work because it'll try to read the prgmCOMPILED as source code.

This is only in Axe source
However, including compiled code is just a bad idea (pre-compiled code won't run correctly), and to include source, we already have prgmPROGRAM.
As for including BASIC programs, I'm curious why you'd need that. Could you elaborate?
Note: This post to me seems it might be bordering on offensive. I do not mean it as such.

Ok, I have a feature 'wish':

When the parser runs into certain errors, mainly the Missing Label, Undefined, and Duplicate errors, could there be an option to 'skip' that line of code when compiling? As in, if this option was chosen, the line containing the offending error would be ignored completely by the parser (as if it were prefixed by a period) Error messages would then have a menu accompanying them (sort of like BASIC) with Quit, Goto, and Skip (if applicable)

This sounds kind of hard though, and so it's ok if it's not really realistically possible, but thanks anyway

Well, I think that in many situations, the user doesn't care immediately whether a certain piece of data will be included or not. Maybe they were typing quickly while making, for example, a menu, and defined Str1 twice But they really just want to test whether the code works and won't care if Str1 is defined incorrectly, and so this might make some debugging a little faster (maybe)

I hope I explained it well enough

Also, I have another request/question: When you use InData(), the data is zero-terminated, but it seems that the 0 is included in the data to be searched: For example, if A=0, and you ran InData(A,Data(1,2,3,0)), it would return 4...Is it supposed to be like this? I think it might be better if the 0 was not included in the data to be searched...

Also, I have another request/question: When you use InData(), the data is zero-terminated, but it seems that the 0 is included in the data to be searched: For example, if A=0, and you ran InData(A,Data(1,2,3,0)), it would return 4...Is it supposed to be like this? I think it might be better if the 0 was not included in the data to be searched...

Exactly.  You generally don't want to search for the zero case.  Usually what you do is handle that separately and then when you're sure the byte is non-zero, then use the inData() search.  Although you can search for it if you don't mind it being part of your data since I don't treat zero as a special case.  The reason it's setup this way is because I'm trying to use the smallest code with the fastest speed, and this was most efficient.

I have a couple suggestions I think would save a little time when compiling.

1. On the compile screen, sort programs by most recently compiled. The most recently compiled program is at the top.
2. Have a way to automatically run programs after they're compiled. This could be an option, or just a different key to press (instead of enter). I guess this would only work if you're compiling for no shell though.

If both of these suggestions are made, then it should only take 2 keystrokes within Axe to compile and run whichever program you compiled last.

An alternate (or additional) idea is to have a button that compiles and runs the most recently compiled program from the main screen. That would only take 1 keystroke within Axe.

I like those ideas, it'd be very fast to code/compile/test repeatedly.

Also, I don't know if this would ever be possible, but Axe inside Doors? For example, I program in Doors sometimes and I have to change Application to compile This is a very weird thing, but maybe you could find a way of getting throught it, Quigibo.

Nevertheless, it's good to see you're hearing to our prays in this long, long topic

I will probably do that; have a pointer in the app that points to a special parsing routine so that external programs like DCS can automatically know where to jump into the app to "externally" use Axe without having to quit the original application.  This is something that Kerm would have to add to DCS, and I'm sure he would if you request it, but I haven't added that functionality to Axe Parser yet.  However, its definitely planned.

Would it work with ASM programs? Can't wait for that