Re: Default extproc syntax not recognized by content assist

On 4/17/2019 6:17 AM, Barbara Morris wrote:

On 2019-04-17 12:21 AM, Joe Pluta wrote:

As Barbara noted, EXT and EXTPGM work without an argument.  I just assumed that EXTPROC worked the same way, and the compiler accepted it cheerfully - and it worked (albeit with fully uppercased names).

Well, it turns out you were right all along, Joe. I'm not sure what I was seeing yesterday. EXTPROC _is_ valid without a parameter. Sorry about the confusion.

I can see it right there in the code for the compiler: Minimum parameters 0, maximum 3.

Thanks, Barbara.  And that happens to be exactly the case that is causing problems with the Outline view of RDi.  If the program specifies EXTPROC with no arguments, the Outline view does not generate a symbol entry with the upper-cased name as it should. So, effectively you cannot use ctrl-space (context assist) to bring up one of those procedures.  And it looks like in certain cases in breaks other context assist as well (I've found though, that hitting ctrl-space multiple times fixes at least that part of it).

I've gotten around it by changing my default to extproc(*dclcase), which has pros and cons.  As long as I use a copy book for my prototypes, all of my RPG code is fine.  I'll just have to remember the *DCLCASE syntax for CL.

I've entered a Service Request for the issue.