RE: Chalk one up for "The Cycle"

Now wait a second.
<snip>
So James saves a bit a time using the cycle, which will be
wasted 10 fold by anybody coming in after him trying to
follow the implicit logic in the cycle program.
</snip>

Many have used the same argument against newer stuff. I don't buy it.

True, however I think it is reasonable to assume that the number of people who
understand "new" ways
will continue to increase. On the flip side, those who understand the old ways
will continue to
decrease.

Since minimizing future maintenance cost is important, making sure an
application can be easily
maintained by an increasing pool of programmers in the future is worthwhile
IMHO.

Would I have used SQL in this case? Yes.
Would I use the cycle when appropriate? Yes.
Would it confuse others? Yes. I once delayed none other
than Jon Paris with a bit of code that used a primary file.
If the cycle was brand new instead of 25+ years old would
some people be jumping on that bandwagon? Maybe.

<lol> Making the experts pause is always good for the ego, but is that always
a good thing?

If the cycle was significantly better than any other option, I could see using
it.

I agree that'd it be interesting to see how the developers would respond if the
cycle was new.


Charles


This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to read,
print, retain, copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be unlawful. Please reply
to the message immediately by informing the sender that the message was
misdirected. After replying, please delete and otherwise erase it and any
attachments from your computer system. Your assistance in correcting this
error is appreciated.