Defining variables

[Ribcakes]

is there any quick way to define multiple variables to the same value, a.k.a. 0?
i would hate to have to use a rediculous amount of code just going

0--> (some variable)

over and over again

Ty
--Rib

[luby]

Well, I'm not sure about 68k, but in 83+ language, we have a DelVar command which lets us do DelVar ADelVar BDelVar C... without a newline to seperate them. Maybe the 68k has something like this?

[DarkerLine]

No, DelVar actually deletes variables in 68k Basic like it would seem to do.

First, I want to ask you, why do you need to define so many variables to 0? You might be better off using a list.

But if you really want to set lots of variables to zero, this code might be slightly better:

{"var1","var2","othervar",...→list
For i,1,dim(list)
0→#(list[i])
EndFor

There's little more one can do unless the variables share something in common. For example, if they're all single-letter variables:

"abcdefgh...z"→str
For ix,1,dim(str)
0→#(mid(str,ix,1))
EndFor

[Ribcakes]

i am essentially a novice at programming.

what i am doing is programming a program to be able to keep track of statistics while watching a tennis match. First serves, second serves, etc... and i do not know any other way of doing it besides using variable for each number

[DarkerLine]

I see. But I know next to nothing about tennis, so I don't think I can help you much.

[Ribcakes]

that's ok, i actually managed to program the entire thing and get it works properly, it just takes about 15~20 sec to start after i hit enter

i tried using that list instead of doing the 0->varname
but it ended taking about 2min just to execute that part of the code
it was faster just doing it individually, which to me, does not make sense

i would assume the only way to speed up the program would be to optimize the code, but unfortunately, the code consists mostly of If Then statements that cannot be combined

thank you for the help though

[DarkerLine]

Can I see the code? Maybe then I'll be able to help you make things faster.

[Liazon]

doesn't 68k support local variables? iirc you could just create new variables and delete them on the go, albeit it's probably slow.

[Ribcakes]

all the variables in my program are already local, thank you for the input though.

and i know this is slightly off topic but i need to ask, for some reason when i try to back up my calc on my comp, it will transfer all the variables but then refuse to transfer the programs

i am getting an 8C010001 error, and i have no idea what that means or where to look it up

help is appreciated
ty
--Rib

[Ribcakes]

here is the code for my program, all of those thick/dark rectangles are actually -->

i do not think that the code can be optimized much aside from a few for loops at the end
thank you for all the help

[AaroneusTheGreat]

To make them easier to read, 68k basic allows comments using the © character. It looks like the copyright symbol, but you put one of those at the beginning of a line, and it'll tell the compiler that the line is a comment, and should be ignored.

This way you can write little notes directly in the program explaining what things do.

[DarkerLine]

Well, you're certainly right in saying that the code can't be optimized much. It needs to be rewritten. I don't mean this to be harsh, but you're obviously not a very experienced programmer, and the approach you've taken to this problem is a hard one to work with.


First, the question of storing data. I suggest you use two matrices, one for singles and one for doubles, with 3 rows and a column for every statistic you want to keep track of. Use only these matrices to store variables that apply to a specific match. Only use a named variable for something that applies to every match at the same time.

As for the current match, I think the best way is to store a value of true or false to a variable called "singles" (this will be 'true' if the current match is a singles match, and 'false' otherwise), and a value of 1 to 3 to a variable called "match".

Second, the question of input and output. I believe using Dialogs is not the natural way to display things in your program. I suggest displaying statistics on the program I/O screen using the Output command, and use the Toolbar..EndTBar command to display a toolbar at the top with options such as "change match", "rename players", and so on. You can use dialogs for specific inputs (such as inputting a player's name), but that's it.

You'd really need two Toolbar..EndTBar blocks: one for each kind of match (because the options might be different). You could structure the program like this:

[Ribcakes]

so, unless i am misunderstanding something, i am going to have a hell of a lot of labels.

i assume that would make the program run faster

part of my toolbar looks like this: