Re: Flags in TI Basic
[Prev][Next][Index][Thread]
Re: Flags in TI Basic
Okay, I'm young and have never seen nor heard of these flags before, but I
do not understand why these flags would not also use "precious memory."
Any data you ever store has to be put somewhere. In fact, I don't even
see the difference between a flag and any other variable. Both are "set"
and can be tested later. That aside, I have read the TI-85 manual cover to
cover, and did not see one words about "flags." I am not one of the
developers, but my guess is, if it doesn't look like a duck, and if it
doesn't quack like a duck, then you don't have a duck.
>Suppose the user is asked to make a menu choice between two options, and
>suppose that later in the program, much later, it is necessary to know what
>choice was made. Ordinarily a flag would be set at the time the choice was
>made. This flag could later be tested to find out what that choice was.
>
>It was suggested by another reader of this group that I could utilize a
>variable as a flag, and it is quite true - I can and do.
>Using a variable however, uses precious memory and leaves a variable in
>existance after the program has finished running. I could delete it (in the
>TI-86), but that in itself uses even more memory. Every byte counts when one
>is maxed out on memory.
>
>Please note that I am not asking how it COULD be handled; I am asking what the
>developers of the TI-85/86 INTENDED.