Re: Default extproc syntax not recognized by content assist

Thanks, Barbara!

I'm not sure about the definition of "can't". EXT, EXTPGM and EXTPROC
can all be coded without a parameter, and they default to the name of
the RPG definition (uppercase).



On 4/16/2019 3:11 PM, Barbara Morris wrote:

On 2019-04-16 12:14 PM, Joe Pluta wrote:

...
dcl-pr myproc extproc(*dclcase) end-pr;

Now I see the export as 'myproc' all lower case. And again I can
prompt. The problem of course is that if you go with *dclcase, you
have to be consistent and use mixed case everywhere. I don't exactly
know how to do that in CL (but only because I haven't tried).

In CL, you put the procedure name in quotes to prevent it from being
uppercased:

callprc 'myproc'

Same with the EXPORT command in your binder source

EXPORT SYMBOL("myproc")

By the way, you can't code EXTPROC without a parameter.

--
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@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com