Re: RDi 9.6 Procedure wizzard

By "header files", I mean separate source members that contain prototypes for service programs, that are included in all the program source members, and the service program source member itself, using the /INCLUDE compiler directive. I use the term header files because they serve the same purpose as C header files. That name's reinforced by the fact that the only ones I have to deal with are from Scott Klement's projects, and all of his end with _H.


Everyone here seems to be in favor of using /INCLUDE to bring service program prototypes into program source members. The disagreement is whether those prototypes should be in the service program source itself or a separate source member containing only the prototypes (what I call header files).



________________________________
From: dlclark@xxxxxxxxxxxxxxxx <dlclark@xxxxxxxxxxxxxxxx>
Sent: Thursday, November 30, 2017 12:07 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.6 Procedure wizzard

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 11/30/2017 12:50:27 PM:

It's a personal preference thing. I prefer separate header files to
compiler directives. I've used both schemes, and I find the header files
are simpler to manage.

On Thu, Nov 30, 2017 at 10:57 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:

I agree. I don't see that header files for RPG add anything over

using

compiler directives to bring in your prototypes.

OK you guys... Enlighten me, please. I know what header files
are in the C sense, but I've never heard of header files for RPG. I only
know of /COPY and /INCLUDE. When were header files introduced for RPG and
how does that work?


Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331




*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************