Ah yes!  It's coming back!  I've tried that in the past, and then accidentally changed the case on the prototype.  The compiler didn't flag it (because it doesn't care!) but the reference never got resolved.  But really, that's no different than messing up the case inside the quotes, so I think I'll give it another shot.  I'd really prefer keeping the inner and outer worlds in sync.

On 2/7/2019 3:29 PM, Barbara Morris wrote:
On 2019-02-07 9:19 AM, Joe Pluta wrote:
Thanks for this, Barbara.   I almost always use EXTPGM (with no parameter) for my prototypes.  Pros and cons, obviously, but I with that syntax, wherever a prototype is used I know exactly which external program I'm calling (of course, in RDi you can get it from the hover, but sometimes you're in the green screen).  EXTPROC is a little harder because of case; I always get confused with that one.  I think there's a way to do it, but I never seem to get it right.


Do you use EXTPROC(*DCLCASE)? As long as you get the case correct when you define the prototype name (or the procedure name, if there is no prototype), you don't have to worry about re-spelling the EXTPROC parameter correctly.

dcl-pr Qp0lGetPathFromFileID extproc(*dclcase) ...
vs
dcl-pr Qp0lGetPathFromFileID extproc('Qp0lGetPathFromFileID') ...



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2021 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.