I've finished the link routines, and they work very nicely but I know there are slight differences between the hardware and I need to make sure I am leaving enough room for variations.  To make the routine as fast as possible and therefore usable in realtime games that have a lot of data to send, the routine is time based instead of confirmation based.  There is a minimum threshold of 10 T-states (1.7 microseconds) which is enough to give me 100% error free byte sending on 2 linked 84+'s and should be enough between all z80 calcs, but unfortunately the Nspire emulation is too slow.  Not sure if there's anything I can do about that.

Anyway, I just need to confirm that this works.  If you have an I/O cable and 2 calculators, preferably 2 different types for example: TI-83+ and TI-84+SE, then please help me test this.  The receiver should run program A which just relays to the screen and then have the other calculator run program B which sends a random byte.  Make sure both the numbers are the same on both calculators and repeat a bunch of times and then switch the roles of sender and receiver.

If there is an inconsistency, let me know which calculator was the receiver, which one was the sender, and the numbers that show up on each screen, thanks!

Its nowhere near done and it won't be released until after 0.4.0 comes out.  Currently, the files are exactly 8 times smaller than the original wave file, but that is with no compression, I will add compression later.  I'm still trying to figure out how to convert the 8 bit signal to a single bit one, this is the best I've got so far but I know I can do a lot better.  If anyone knows the algorithm or where I can find it, that would be really helpful!  Especially if you know how the RealSound algorithm works or similar player.

Here is a sample executable, it doesn't sound good, but at least you can hear it on wabbitemu.  Its awful on a real calculator though, so test it on the emulator.

This is for all assembly programmers who want to develop Axioms for Axe, you can post your questions, related bugs, and other concerns here.  Although I have not actually finished the Axiom feature, I have finished a template for the format I am most likely to use.  It is possible that there could be some very minor changes, but you will easily be able to compensate for those.  I just want to release this now so people can start writing their routines in preparation for this feature.

I included the SDK as well as an example Axiom that shows how some of the current functions could be written as Axioms.  Unfortunately, I realized that it will not be possible to redefine the token names as I was planning since the hook would take too long to search through the program to figure out which Axioms are used in that source and then search through those appvars every time a token is displayed in the editor.  The slowdowns would be too great especially for larger libraries.

Anyway, happy programming!

Has anyone noticed that there are a lot of companies out there in the tech sector with really ambiguous names?  I did a quick Google search with some popular prefixes and suffixes and these were the results.  Basically, if there was any doubt as to if there existed a well known professional and legitimate company with the same name (or some other product, service, definition, etc.) on the top 5 entries on the first Google search results page then I did not include it.  I guess it just goes to show you how uncreative people really are.

It is very important you read all of this before you vote.  This is a crucial part to the future of Axe Parser.

The original concept behind going through the trouble of renaming some of the Tokens is that I am very quickly running out of intuitive TI-BASIC tokens to use for more complicated Axe Commands.  I've often resorted to using the ^r or sometimes even the double ^rr but that's not going to cut it soon.  In this last version, I was all out of sprite tokens, so I used what was left in the drawing menu: Tangent().  The name has no meaning to the intended function and may force one to read the documentation before figuring out what it might be used for.

This is okay though.  I realize that a lot of TI-BASIC programmers are used to their tokens and they know where they are on all the menus lightning fast.  If you hear the word "Str1" you might immediately think "[VARS][7][1]" as I usually do.  But if you hear "Bitmap()" you have no idea where it might be.  The catalog isn't in alphabetical order either so that doesn't help much (maybe I can change that with hooks in the future but I'm unsure).  So there is a concern that you have to learn new shortcuts.

There are many many new commands still to come.  For my example, I will mention the commands for reading from archive.  There would need to be an openfile and a readbyte command.  It is entirely possible that I just use maybe log() to open the files and prod() to read a byte, there is no problem with that.  But I imagine the code is much more readable with Open() and ReadByte() for instance.  This is not an isolated case, there are more than 20 other commands I can think of that don't have any meaningful tokens.

One other advantage of renaming some tokens is that often in BASIC, commands such as int() have totally different uses in Axe.   This can ease any potential misuse since the new names imply that the interpretation of the commands have changed.  While tokens that have the same name will be interpreted as working the same way in both Axe and BASIC.

So, if I start using the new token names, then that raises the new issue of documentation.  Sure, it may be possible to document both in the commands list, and maybe even the user's guide, but not having a single standard can get very confusing when reading other people's source code, writing your own tutorials or routines, and even regular conversations like asking for help and fixing code.

I could still offer the option of using the old tokens but just have them minimally documented (like a simple table that tells you the equivalences between tokens).  That way, it encourages the new standard among the forums and when documenting the code.

If I have the tokens be completely "Mandatory" then I can hook the program editor so that the tokens are automatically enabled when editing Axe programs and then automatically disabled when you quit to the home screen or edit a regular TI-BASIC program.  There could be an option to toggle this behavior in the parser even if the old names names are documented or undocumented.

The last thing I'm going to throw out there: These are only name changes.  The actual position in the menus for each token does not change and all past and future source code is totally compatible since the tokes themselves are still the same, only the physical letters displayed on the calculator are affected.

Please ask more questions if you want clarification on something or want to bring up another point.  You can change your vote at any time.

I've decided to release the source code for all templated commands the compiler uses when parsing.  I challenge anyone to improve the code

You'll have to ignore the cryptic scripts that surround the routines and it probably won't be very obvious what is being done in each one of them.  If you see any routine you think you can get from the start to the finish more efficiently with equal or lesser size, alert me!  If you have any specific question just ask.

Some of the inefficiencies I can't do anything about by the nature of the way the parser currently works, but I plan to correct this eventually (like the jr's at the beginning of the subroutines)

This might also benefit anyone who is trying to transition from Axe to assembly since Axe is for the most part just cookie-cut out of this template.

Okay, I noticed that recently, there was the addition of the little chat box at the top of the page.  Its pretty cool, but it was kinda distracting so I hit the little minus sign on the right to move it out of the way.  However, it still constantly refreshes the page every few seconds even when the chat is not open and its really getting annoying, especially when I have multiple tabs of omnimaga open.  Is there a way to turn it off or some type of setting I can change?