Re: Feedback on iProjects - good, bad and ugly

On 2017-04-24 1:48 PM, Charles Wilt wrote:

...
​Can you elaborate on RPGLEINC?

First I recall hearing about it...

A quick google search turns up a blurb in the info center
"If the path does not end with a suffix (for example ".txt"), the compiler
will search for the file as named, and also for files with suffixes of
".rpgle" or ".rpgleinc".
​
​It doesn't appear in the drop down for source member types....but it
appears to work and RDi appears to recgognize the RPGLE syntax in the
member...

So should our include members use RPGLEINC as a source type?

The blurb in the info center is describing RPG's rules for finding /copy files in IFS. So that bit of doc doesn't apply to source physical file member types. But that _is_ the reason that RDi supports the source member type .RPGLEINC as RPGLE code.

PDM/SEU doesn't know about RPGLEINC, but it has always been possible to use any source member type you like. So when you don't need SEU to know that your source member has RPGLE code any more, then indeed it's a good idea to use RPGLEINC as the source member type for includes. That allows you to still edit normally using RDi, and it has the benefit of telling RDi, iprojects, and other humans, that it's not a compile-able type.