|
(From Michael:) ...while I use booleans (as I would in any language), the only indicators I use are for working with display and printer files, and *INLR. I can't imagine using the cycle.... ==> I don't use the "numbered" indicators anymore except for the INDDS. Overlay it with meaningful names, and overlay *IN into a data structure and/or use named constants. For ER or NF conditions, couldn't we get file status from an INFDS data structure for that file, and even "name those status codes"? Level check indicators are better for performance where appropriate, but changes to the sort order, or "exotic" break conditions (for example, ranges of accounting codes grouped for totals) or some other things can get real complicated real fast. Maintenance is much easier with greater flexibility. I did get an appreciation for the built-in "grouping" and "totalling" cycle logic though when I had to "simulate" them when using SQL for input... :0) --Alan
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.