Re: EVAL YES = 'N'

[Dan <dan27649@xxxxxxxxx>]

Buck,

Most of us in this forum have been there, done that, and wrote the check.
It may be helpful to note that this particular application was written from
scratch 6 years ago.  All of the code on this system was written in the
past 11 years.  Three of our six developers have never written a line of
/FREE or **FREE code.  One recently retired.  I have an inkling that the
author of the work being discussed here may be heading that way soon.

As for refactoring, I would do it in a heartbeat if it didn't mean crushing
someone's ego.  That's a longer story than anyone would be interested in,
but suffice to say, I only touch what I need to touch.  In this particular
case, I don't actually need to change anything that involves the YES
variable in this program.

- Dan

On Wed, Mar 21, 2018 at 10:22 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

> On 3/20/2018 7:07 PM, Dan wrote:
> ...
> When I was a littler child, I crashed my sled into a tree.  Broke my
> nose.  My nose works: I can breathe through it, but it's far from
> beautiful.
>
> I've seen code like that.
> I've written code like that.
>
> Imagine RPG II that looks like this:
> C   21N80 50
> CANN12NMR             GOTO SKIP1
>
> This was common in the 70s.
>
> Then I come along in the 80s and I need to modify it on my
> fancy-schmancy S/38.  I don't have 128 character names yet; I don't even
> have mixed case yet.  But I'm a genius (aren't all teens?) and in my
> youthful 'wisdom' I decide to turn that complex indicator mess to a
> clearer code block: