Since no other language has the cycle (that I'm aware of) in today's world
where you might not be the one to maintain the program, more currently
traditional styles of managing I/O is vastly preferred. Regardless of your
adoration for the cycle, it's no longer commonly used. Sure it's easy in
the right circumstance, however 99.5% of the students coming out of school
have never seen a cycle program. That makes it your problem, not theirs, to
make sure they can maintain what you built.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James
H. H. Lampert
Sent: Tuesday, June 12, 2018 1:19 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: the cycle that never ends
On 6/12/18, 10:42 AM, dmmueller@xxxxxxx wrote:
and should I be embarrassed to say, we still have some of those cycle
programs still running.... and with each upgrade, they still work :)
Nothing to be embarrassed about.
What should be embarrassing is when people AVOID using The Cycle in
situations where it is the correct tool for the job . . . and end up
"walking" through a file when they can "ride" through it (or writing their
own "do until the user exits" loop when, simply by tying LR to whatever the
user does to exit, e.g., tying it to INKC, they can use a built-in
event-loop).
--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
