× 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.


  1.  Home
  2. WDSCI-L
  3. April 2019

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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.