I suppose I would prompt the line then hit accept so it has all the keywords, as I do prefer that. However I don't mind having an IF THEN line in CL. The idea to always do a DO to more easily allow for future enhancements is something I may think about now.
Thanks,
Kurt
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
Sent: Friday, October 23, 2009 9:15 AM
To: Midrange Systems Technical Discussion
Subject: RE: ENDIF in CLP
i usually use the DO construct simply because that today only one action
needs to happen based on that criteria but should there later be more
actions/commands to execute on that condition i do not have to change the
conditional statement but just add the new code to execute.
Thanks,
Tommy Holden
From: "Dennis Lovelady" <iseries@xxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 10/23/2009 09:11 AM
Subject: RE: ENDIF in CLP
Sent by: midrange-l-bounces@xxxxxxxxxxxx
That said, if I were taking ownership of the program, that EndIf would
be deleted so fast...
I wouldn't delete it; I'd turn the statement into a THEN(DO) protocol. I
dislike and distrust IF statements that can have only one action, and lack
closure.
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"I'm sincere. I'm really curious. I care what people think. I listen to
answers and leave my ego at the door. I don't use the word 'I.'"
-- TV personality Lary King in Psychology Today
-Kurt
midrange.com
