Reinventing Code

Not using a feature that the language has had for over 30 years
is foolish and wastes company time reinventing a "new" method
just to say you can do it. L1(et al) & and for that matter M1(et al)
have a place in the big picture.. I have heard the ranting & raving
over bad coding practices for years... some even have a valid point,
but to ignore somthing because:

(a) you don't understand it 
(b) you don't like it
(c) it's not structured code
(d) that's not the way you were taught
(e) it uses the "cycle"

is a serious oversight....

I don't care for some of the newer "features" because I think it 
just clouds the picture for people who have to follow your snazzy
way of writing code, but that doesn't mean I won't try to learn the
new method for the sake of some future project that would require
that particular feature... A good bit of the "new" features are very
handy & strangely enough, "they" replace things programmers have been
doing for years(the hard way)...I have been writing programs for a good
mamy years now and the methods I use are out of habit, not "style",,,

I was taught(at a service bureau) you "will" write code that "anybody"
can follow or you will no longer have a job here... That was years ago,
and I have used that "style" ever since..

Just my ranting & raving.. Not pointed at anyone in particular...
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---