Re: Cycle Processing vs. Doing it my way

I wanted to stay out of this holy war, but I just couldn't.  :)

flamethrower(*on)

Even if you don't want to write new programs using the cycle, (and you have
EVERY right not too), if your job brings you anywhere near a legacy cycle
program (and there are millions out there), then you'd better learn how the
cycle works, and you'd better learn it fast.

If you are my employee and couldn't handle maintaining or making major mods
to a cycle program, I have no use for you.

It IS VERY SIMPLE!  remember the old spacing templates we all carried in
our pocket to read printed rpg code?  it had a simple flow chart on the
back that said all you needed to know about the cycle.   It had about ten
boxes and two or three branches.

Talk to anyone who knows the cycle, and they could explain it simply in a
few minutes if you weren't too hard headed to listen.

If you can't read and understand that flowchart, then I have no use for
your services either.

If you refuse to learn something that WILL help you when you need it, then
I have no use for you, because you are too hard headed to work for me.

I use the cycle in about 3% of new programs I write.  If it has a printer
file and control breaks, I use the cycle.  It's a no-brainer in my view.

What are you going to do if you run across one of my (or any of the other
millions) programs that use the cycle.

flamethrower(*off)

On that note, I hope everyone has a great weekend!

Rick