RE: /copy surprise

Barbara,

I understand what you're saying. I wasn't quite clear enough. That's what
I meant. .-)

By the same token, any /free, /end-free directives in the /copy member would
have no effect when returning to the main program, right? That is, as I
understand you, whatever "free" state the main program was in before the
/copy will be honored after returning to the main program.

Jerry C. Adams
IBM i Programmer/Analyst
I speak Spanish to God, Italian to women, French to men, and German to my
horse. - Charles V, Holy Roman Emperor
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Barbara Morris
Sent: Thursday, May 19, 2011 5:09 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: /copy surprise

On 2011/5/19 2:22 PM, Jerry C. Adams wrote:

... In David's case, it would seem, the /end-free directive in the main
program is superfluous; I'm guessing here that the /free is, also,
superfluous ...

No, the /free is necessary in the main source if /end-free was coded
before the /copy. The freeness (freeity?) in the main source is restored
after the /copy is processed. So if it was non-free before the /copy,
then it is assumed to be non-free after the /copy. It doesn't matter
what happened in the /copy file.