Ah ok I see now.

Oh I didn't knew the 89t had such values. On the 84+ I think it's 14 digits + exponents, right?

I doubt it'll show up for a few days (it has to be reviewed), but I just wrote a nice review for BatLib on ticalc

it's awesome

BatLib is almost out of the Beta stage. Since the last version, there have been major changes. Any programs made with the last version of BatLib will not work with the new version. The changes:
1) sum( is no longer used. Apparently DCS7 uses the sum( command. BatLib now uses dim(.
2) All instances where the arguments use "VarName",Type is now in the form Type,"VarName". This way, if the variable is a token (like Str1 or Pic3), the type can be omitted.
3) Removed some stuff that wasn't needed, saving some memory

I also finally made a sprite editor so that making tilemap or font data will be easier. I will upload that program in a "Demo" topic.

Here is the new version of BatLib as well as the updated readme.

Also, one of the features that has been with BatLib from the beginning is one that I don't believe I have talked about. I call it stringing command. As an example, say you have some code that looks like this:
dim(29,0,8,0,8,2
dim(99
dim(10,67
dim(43→A
dim(29,0,8,0,8,2
You can actually string them all together with one dim( command:
dim(29,0,8,0,8,2,99,10,67,43,29,0,8,0,8,2→A
This will save speed and memory, so if you can string commands, you should.

Oh, I still plan to add a whole lot more, but I had to get all the syntaxes finalised and I had to make a final decision about which token to use. Now that that is done, I can go fix everything up and I can start adding new functions.

Before I release the actual BatLib app, I have a question. Should I use the syntax to read variables as Type,"VarName" or should I just use "VarName", but require a prefix byte? If I do the prefix method, to read prgmBATTLENG, instead of 5,"BATTLENG", you would use "[BATTLENG". This would save memory and speed, so I like this method better. It will be the same syntax as the CopyProg program.

Okay. I have been working with the modified version and it actually cut down the size of BatLib, also. The only place this uses more memory is when you could have omitted the type to begin with. It is still faster though and it will help make other commands faster and smaller.

8897 bytes
I still have stuff to remove or optimise, too, so I will have plenty of room to work with for the next few functions.