|
"Michael Ryan" <michaelrtr@xxxxxxxxx> wrote:
I can't imagine using the cycle. While I know people still use level indicators, and god love 'em, I just don't use them.
I've never once used a level indicator, and indeed, I'd have to do a fair amount of reading in order to know *how* to use them.
On the other hand, I write simple (and frequently unconventional) cycle programs with some regularity, and I do so for two reasons:
1. In an event-driven interactive program, you obviously need a "do until the exit condition is raised" loop. Guess what: RPG has one built in. It's called The Cycle.
2. In a program that goes through an entire file, say, to update it, or to check records for problems, and repair them (interactively or otherwise), why make the program WALK through the file, when it can climb onto The Cycle, and RIDE through it?
Either way, I end up with a significantly shorter program by using The Cycle.
Going back to indicators, I've long had a convention of using multiples of 7 ("we got lucky") for indicators that mean something good has happened, and multiples of 13 ("no such luck") for indicators that mean something bad has happened (or simply that something wasn't found).
-- JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
