Show Posts
1981
News / Re: Axe Contest poll and judging starts
« on: October 02, 2010, 06:03:17 am »
Whoops lol, I knew impartial wasn't the right word, but I knew you guys would get the idea 
|
| A basic example (also attached): Code: [Select] .GRAVTEST | Pseudocode: Code: [Select] Header |
1990
TI Z80 / Re: My First Quantum Translocator
« on: October 01, 2010, 09:58:44 am »
By the way, just to clarify something: a lot of the optimizations were just code order and logic optimizations, but a decently sized part of the optimization was that I changed how subroutine CY works. Instead of storing the result into r6, it now simply returns the value directly to where it was called. I adjusted all your existing calls to subroutine CY already, but in the future, instead of doing something like:
And just a note, using sub() like this can sometimes cause an argument error when compiling if you leave out the closing parenthesis. If you get this error, just add the closing parenthesis. (Press PRGM when the error is displayed to go to the exact point in the code where you need to add the parenthesis)
Code: [Select]
sub(CY,3
If r₆Just do:Code: [Select]
If sub(CY,3And just a note, using sub() like this can sometimes cause an argument error when compiling if you leave out the closing parenthesis. If you get this error, just add the closing parenthesis. (Press PRGM when the error is displayed to go to the exact point in the code where you need to add the parenthesis)
1991
Axe / Re: Routines
« on: October 01, 2010, 09:53:36 am »
Yes, and it doesn't appear to work correctly when trying to store it into a string. Perhaps this is something Quigibo should look into fixing?
1992
TI Z80 / Re: My First Quantum Translocator
« on: October 01, 2010, 09:48:14 am »
Shaved 216 bytes off the executable 
Not bad, considering saving 216 bytes in a 1519-byte executable is 15% gone with just code optimizations.
Not bad, considering saving 216 bytes in a 1519-byte executable is 15% gone with just code optimizations.
1993
Axe / Re: Routines
« on: October 01, 2010, 08:57:59 am »
I just helped someone out with a specific case of writing a value to an OS list, so I figured I'd post this generic routine for others to use while I'm at it.
A note about list names: for L1 through L6, you can just define the name with something like:
And now the actual routine:
A note about list names: for L1 through L6, you can just define the name with something like:
Code: [Select]
"L₁"→Str1But for custom lists, you must do the following:Code: [Select]
[015D]→Str1
"NAME"
[00]And now the actual routine:
Code: [Select]
.Write a series of 2-byte values to an OS list (Pointer to name, number of elements, pointer to list of 2-byte values)
Lbl OSL
GetCalc(r₁,r₂*9)→r₄
r₂→{r₄-2}ʳ
For(r₅,0,r₂-1)
{r₅*2+r₃}ʳ→float{r₅*9+r₄}
End
Return
1994
Axe / Re: Custom lists
« on: October 01, 2010, 08:37:56 am »
Enjoy 
Code: [Select]
Lbl RET
Disp r₁►Dec
[015D]→Str1RV
"AVLIB"
[00]
If GetCalc(Str1RV,9)→Z
1→{Z-2}ʳ
r₁→float{Z}
End
Return
1995
Axe / Re: Finding / listing programs
« on: September 27, 2010, 10:03:00 pm »i'm guessing there's an address in ram that begins where all the programs are stored, and then the first few bytes of the program indicate the size of said program, whether it's archived etc. then program name/data. so to get all the names, you would have a loop reading off the program name, copy it to a safe ram area, then skip ahead [size of program] bytes to the next program.
I believe their programs may read from the VAT (Variable Allocation Table), which contains information about every data structure on the calculator, whether it's a variable, list, program, app, etc.