Author Topic: Features Wishlist (Read 703157 times)

aeTIos · « **Reply #2250 on:** May 09, 2011, 09:42:49 am »

My wish: Axe does only include routines in included files if they're called. All routines end in return, so it won't be too hard to implement....

Freyaday · « **Reply #2251 on:** May 09, 2011, 09:43:05 am »

How about an option to enforce it or not?
The reason I'm against it is because Axe programs need so much space that any savings are precious, and I've saved hundreds of bytes by writing my code to eliminate as many closing parenthesis as possible

ZippyDee · « **Reply #2252 on:** May 09, 2011, 09:49:43 am »

Quote from: aeTIos on May 09, 2011, 09:42:49 am

My wish: Axe does only include routines in included files if they're called. All routines end in return, so it won't be too hard to implement....

Not true...sometimes people end routines in Goto. It's certainly not as simple as just looking for a return after a label. There's a lot more that has to be taken into account.

aeTIos · « **Reply #2253 on:** May 09, 2011, 09:51:45 am »

But real routines are called via sub(. If they end in a goto, you cant call it via sub( or your program cant be closed... (I have experienced this several times when I learned axe xD)

ZippyDee · « **Reply #2254 on:** May 09, 2011, 09:53:07 am »

Unless it goes to another routine that has a return...

Freyaday · « **Reply #2255 on:** May 09, 2011, 09:54:49 am »

Oh, a way to make the backup create a new backup under a different name, so that when you're trying something new and you're not sure if it'll work or if you'll like it, you can have the old one backed up and in case you do or it does, you have the new one backed up as well.

aeTIos · « **Reply #2256 on:** May 09, 2011, 10:26:51 am »

Yeah, thats a good idea!

collechess · « **Reply #2257 on:** May 09, 2011, 07:55:57 pm »

Line(-1,x1,y1,x2,y2) or Line(-1,x1,y1,x2,y2)T

Erases a line from (x1,y1) to (x2,y2)

Michael_Lee · « **Reply #2258 on:** May 09, 2011, 08:40:41 pm »

A workaround:

Invert the screen, use Line(), then invert the screen again?

Code: [Select]

DrawInv
Line(x1,y1,x2,y2)
DrawInv

Compynerd255 · « **Reply #2259 on:** May 10, 2011, 10:33:18 am »

Quote from: Michael_Lee on May 09, 2011, 08:40:41 pm

A workaround:
Invert the screen, use Line(), then invert the screen again?
Code: [Select]
DrawInv Line(x1,y1,x2,y2) DrawInv

But that's hecka slow. I know that TI-BASIC allows you to draw both white and black lines with the fifth argument: Line(x1, y1, x2, y2, color). But this workaround does work until that update is made.

Freyaday · « **Reply #2260 on:** May 11, 2011, 08:47:43 pm »

Some way to get the current position of the Text cursor.
Maybe something like
Text ->X
Would make X the format used by Text(X), And
Text ->X,Y
Would be what is used in Text(X,Y)

ztrumpet · « **Reply #2261 on:** May 11, 2011, 09:07:01 pm »

{_E86D7}^r->X should do Text->X
{_E86D7}->X and {_E86D8}->Y should do Text->X,Y

Compynerd255 · « **Reply #2262 on:** May 12, 2011, 12:03:13 pm »

Quote from: ztrumpet on May 11, 2011, 09:07:01 pm

{_E86D7}^r->X should do Text->X
{_E86D7}->X and {_E86D8}->Y should do Text->X,Y

Are those BCALLS, or are they memory locations?

Oh, and I have a feature request that I think we would all love: Defining tokens as constants. Simply put,

Code: [Select]

9000→X
X+9000→X
If X>9000
Disp "Its over 9000!"
End

could be

Code: [Select]

#Define(Xmin, 9000)
Xmin→X
X+Xmin→X
If X>Xmin
Disp "Its over 9000!"
End

Then, symbols could be defined relative to each other, as in ASM, and then we could also do other things with it as well. Symbols could also be undefined, and redefined later in the program.
A way you could code it:
- When a #Define instruction is encountered in the program, it reserves one of the spaces used for 32 Axiom commands to store up to 32 symbol definitions (limiting the user to 4 Axioms).
- Every time the token is encountered, the number is parsed instead.
- When an #Undefine is encountered, simply remove the symbol.

ztrumpet · « **Reply #2263 on:** May 12, 2011, 03:21:52 pm »

Quote from: Compynerd255 on May 12, 2011, 12:03:13 pm

Quote from: ztrumpet on May 11, 2011, 09:07:01 pm
{_E86D7}^r->X should do Text->X
{_E86D7}->X and {_E86D8}->Y should do Text->X,Y
Are those BCALLS, or are they memory locations?

Memory locations.

Quote from: Compynerd255 on May 12, 2011, 12:03:13 pm

Oh, and I have a feature request that I think we would all love: Defining tokens as constants. Simply put,
Code: [Select]
9000→X X+9000→X If X>9000 Disp "Its over 9000!" End could be
Code: [Select]
#Define(Xmin, 9000) Xmin→X X+Xmin→X If X>Xmin Disp "Its over 9000!" EndThen, symbols could be defined relative to each other, as in ASM, and then we could also do other things with it as well. Symbols could also be undefined, and redefined later in the program.
A way you could code it:
- When a #Define instruction is encountered in the program, it reserves one of the spaces used for 32 Axiom commands to store up to 32 symbol definitions (limiting the user to 4 Axioms).
- Every time the token is encountered, the number is parsed instead.
- When an #Undefine is encountered, simply remove the symbol.

I second the request. It's a great idea.

yrinfish · « **Reply #2264 on:** May 12, 2011, 03:29:26 pm »

I like that idea, but not #Define but #def because that fits better, and maybe other symbols that are shorter...

Author Topic: Features Wishlist (Read 703157 times)

aeTIos

Re: Features Wishlist

Freyaday

Re: Features Wishlist

ZippyDee

Re: Features Wishlist

aeTIos

Re: Features Wishlist

ZippyDee

Re: Features Wishlist

Freyaday

Re: Features Wishlist

aeTIos

Re: Features Wishlist

collechess

Re: Features Wishlist

Michael_Lee

Re: Features Wishlist

Compynerd255

Re: Features Wishlist

Freyaday

Re: Features Wishlist

ztrumpet

Re: Features Wishlist

Compynerd255

Re: Features Wishlist

ztrumpet

Re: Features Wishlist

yrinfish

Re: Features Wishlist