Re: Replacing *ENTRY PLIST

Hi Charles ... I think RPG compiler or pre-compiler is not able to pair PR
Prototype and PI Progam Interface without a fully qualified name ...
Personally I never use '*n' for PR, PI or parameters too: I don't like it
and when I try to debug or understand those lines of code with '*n' it's
like coming back to times with RPG Indicators

When I have a program with a Program Interface PI (ex *entry plist) I code
it with a fully qualified name and I keep the PR in a different source
included with a /COPY and ask to RPG compiler to check them every time I
compile my source code.

HTH
Roberto




Il giorno mer 4 set 2019 alle ore 19:27 Charles Wilt <charles.wilt@xxxxxxxxx>
ha scritto:

Just ran across some code...

// in a MYINC(MYPGM)
dcl-pr myprogram extpgm('MYPGM');
parm1 char(10) const;
end-pr;



//in MYPGM.SQLRPGLE
/copy MYINC,MYPGM
dcl-pi *n;
parm1 char(10);
end-pi

I was surprised it compiled successfully...no errors/warnings

When I changed the PI to
/copy MYINC,MYPGM
dcl-pi myprogram;
parm1 char(10);
end-pi

Then I got the SEV 20 errors about the missing CONST I expected to see.

Can somebody refresh my brain as to why the compiler didn't throw the
expected errors with the unnamed PI?

Thanks!
Charles
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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