× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Dave,

I use the
/define & /undefined...

But, in the compiler listing, you still get a whole bunch of copy-books... Oh well...


-Ken Killian-

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of dlclark@xxxxxxxxxxxxxxxx
Sent: Thursday, November 30, 2017 2:13 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.6 Procedure wizzard

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 11/30/2017 01:57:53 PM:
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).


We currently place all of a particular service program's prototypes, templates, and related constants in their own (single) copybook and INCLUDE it in both the service program and the calling programs.

The only complaint we get with that, around here, is if a service program has, say, 100 service procedures in it and the caller is only using one of those service procedures then the programmer doesn't like having to INLCUDE all 100 prototypes along with their templates and related constants. Their issue is that even if they compile with the *NOUNREF keyword they still get a larger compiled object than if they only hardcode just what they need for that one service procedure.

As for the issue of whether those prototypes should only exist in the service program (no separate copybook)... I'd be in favor of that is there were a compiler directive to extract just the prototype(s), template(s), and constant(s) needed by the caller. From the talk, there seems to be such a thing. What is it? Or is this just a tricky way of inserting compiler directives into the service program source that allows the caller to use additional compiler directives to selectively extract source when you INCLUDE the actual service program's entire source?


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.
*********************************************************************************************
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.