calc slowing down
[Prev][Next][Index][Thread]
calc slowing down
>
> Rene Kragh Pedersen wrote in message <34F85A3A.41C6@daimi.aau.dk>...
> >Jody wrote:
> >
> >[snipped text about breaking programs and picking up again to save mem]
> >
> >> You need to convert the 92 to a 1), display that
> >> number and stop the program. The effect will be very similar to what
> >> the user would see if you had just used an input. And, just like if
> >> you had used an input, the user will then press enter.
> >
> >To make sure, you could write "press [enter] to continue" instead of
> >keeping the user guessing.
> >Personally I hate waiting for a program to continue, only to find out
> >that I was supposed to magically know I had to press something to
> >continue.
> > - But it's a good idea you have there. Abolutely!
>
> The only time I have Ever seen a prog slow down wile running is if is a game
> that loops through the same code over and over again and has goto's in If
> Then statement.
>
> sopping a restarting the prog will solve this, so will cleaning up after a
> then.
>
>
Even if the code is perfect with all the end's to the loops in the
right places and no goto's inside of loops and stuff like that, I
think that it will still eventually slow down. Especially for
extremely loooonnnnggg stuff. The worst that I have ever seen was when
I was writing my own version of monopoly. The first version wasn't
very clean (I didn't know about using goto's inside of loops), but
even the second, clean, version would slow down and eventually
ERR:MEMORY.
Jody Snider
jody1@alaska.net