Laurence Reeves wrote: > Except... I have this vague memory that TT was going to make FOR loops > hold onto the initially supplied values, evaluate how many steps they > looked as if they needed to do, then do exactly that many, scaling the > variable to neat values along the way. Maybe he didn't. As far as I can tell from a 10 minute study of the SBASIC sources he still uses the method you described for QDOS/Minerva (10 minutes aren't really enough to completely understand that code, but I think I got an impression ;-). Cheers, Marcel
- RE: [ql-users] NEXT in FOR-loop Mel LaVerne
- RE: [ql-users] NEXT in FOR-loop Claude Mourier 00
- RE: [ql-users] NEXT in FOR-loop Ian . Pine
- RE: [ql-users] NEXT in FOR-loop Ian . Pine
- Re: [ql-users] NEXT in FOR-loop Dave Walker
- RE: Re: [ql-users] NEXT in FOR-loop Ian . Pine
- RE: [ql-users] NEXT in FOR-loop Claude Mourier 00
- RE: Re: [ql-users] NEXT in FOR-loop Steve Howe
- [ql-users] Q40/Q60 Giorgio Garabello
- RE: [ql-users] NEXT in FOR-loop Laurence Reeves
- Re: [ql-users] NEXT in FOR-loop Marcel Kilgus
- Re: [ql-users] NEXT in FOR-loop Tony Firshman
- Re: [ql-users] NEXT in FOR-loop Marcel Kilgus
- RE: Re: [ql-users] NEXT in FOR-loop Ian . Pine
- Re: [ql-users] NEXT in FOR-loop Mel LaVerne
- Re: [ql-users] NEXT in FOR-loop Mel LaVerne
- Re: [ql-users] NEXT in FOR-loop Tony Firshman
- RE: [ql-users] NEXT in FOR-loop Norman Dunbar
- RE: [ql-users] NEXT in FOR-loop Claude Mourier 00
- RE: [ql-users] NEXT in FOR-loop Ian . Pine
- Re: [ql-users] NEXT in FOR-loop Richard Zidlicky
