new way to do subroutines in basic

[darkstone knight]

the program:
goto S
lbl 1
//subroutine 1
end

lbl 2
//subroutine 2
end

lbl S //start
//all other code

now, to call a subroutine, use this code: (17 bytes)
2→A
while A
DS<(A,1
goto 1 //replace 1 whit the subroutine's number
end

what do you guys think??

[Weregoose]

It's good that you found this out – it shows that you're really understanding the way the interpreter works. It's also good to keep such "subroutines" at the top of the program, since all Goto's would find the labels up there much faster. However, since one of these blocks is liable to get called prematurely (being the first thing encountered in a program), we'll need to take some precautions.

We could use If rand=.7455607728 as a means of conditionally activating the subroutine, and then store 1 to rand somewhere else in the program as a way of telling the calculator that it's time for that particular routine to be run. A second subroutine can be set up immediately after the first one, with If rand=.4911215451 being a different door, and 2→rand being the key to unlock it, and so forth. The cool thing about this is that when rand is run twice, the number will be different. So, each routine will only be accessed once until its respective seed is reproduced.

I believe a similar implementation is written into the subprograms article on TI|BD.

[DarkerLine]

I'd actually stay away from storing to rand unless it's really necessary. Resetting the seed often makes programs that rely on random numbers disappointingly predictable.

[darkstone knight]

a, this is the second time i found out someting that did already exist :hmpf:

annyway... thanks

[simplethinker]

[elfprince13]

you can use lists as a function stack if you want to properly implement variable scope.

[nitacku]

This subroutine jump method got me thinking... Since putting DelVar in front of a loop will make the interpreter skip it when it's in skip mode, could this be used in anyway. Well this is the best I could come up with. It's not the prettiest method, but there might be a few situations where it could be useful.

[Galandros]

I discovered a possible speeder way to pass subroutines in the beginning of code. Specially in giant programs, I think.
If 0
Then
lbl 1
//subroutine 1
end
lbl 2
//subroutine 2
end
End

Passing the If block may be better than Goto... But overkill the use of If <strange variable or rand>=<igually strange value>...

[darkstone knight]

it doesnt actualy return to the place where you called it

[Galandros]

[calc84maniac]

While 0 is a bit better than If 0:Then.

[Harrierfalcon]

I typically do this for internal subroutines.


PROGRAM:A
:If min(H!={1,2,3,4,5...n
:/pi/→H
:While H=1
:...
:Return
:End
:While H=2
:...
:Return
:End
:...
:While H=n
:...
:Return
:End
:...
:3→H
:prgmA

I have no idea if this is the most efficient way, but it makes the most sense to me, as it 1) Doesn't involve icky goto/lbls and 2) only requires two lines--instead of yet another loop of some sort--to call the subroutine.

[darkstone knight]

memory leaks, ehh?

[Galandros]

[Harrierfalcon]

It does. We have vurrobin to thank for that, IIRC.

[darkstone knight]

only issue i can see, that the program does kinda weird if H is set at the beginning of the routine...

mayebe if you use a var, like X, it will get changed that often it doesn't really matter