Definitely best practice to use ExtProc(*DclCase) with RpgUnit
______________________________________________________________________________________
Edmund Reinhardt
905-413-3125
IBM Canada Ltd Rational Developer for i Access Client Solutions
Architect
[1]
https://www.linkedin.com/in/edmundreinhardt/ [2]
http://ibm.biz/rdi_hub [3]
http://ibm.biz/IBMi_ACS
----- Original message -----
From: Justin Taylor <jtaylor.0ab@xxxxxxxxx>
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
To: wdsc <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] Re: [WDSCI-L] Mixed case in object filters?
Date: Fri, Oct 23, 2020 1:31 PM
That's kind of what I figured, but it can't hurt to ask. Explicitly
using
mixed case procedure names can be problematic, but since nothing should
reference the RPGUnit service programs it might be a non-issue.
Thanks
> ---------- Forwarded message ----------
> From: Brian Parkins <goodprophet.bp@xxxxxxxxx>
> To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
> Cc:
> Bcc:
> Date: Fri, 23 Oct 2020 12:41:16 +0100
> Subject: Re: [WDSCI-L] Mixed case in object filters?
> In order to achieve mixed-case procedure names, you use the RPGIV
> EXTPROC keyword. (Otherwise the compiler converts the names to
uppercase.)
>
> I just did a little test using EXTPROC(*DCLCASE) and the RSE view
> displays the (mixed-case) procedure names perfectly. (NOTE: I believe
> *DCLCASE can only be with in free-format. Otherwise you'll have to
> specify EXTPROC('MixedCase').)
>
> In other words, the solution is with coding, not RSE.
>
> Dcl-PR Proc1 Packed(5:0) ExtProc(*DclCase); >>>>>>> RSE
> displays as 'Proc1'
> Dcl-Parm Parm1 Date(*ISO) Value;
> End-PR;
>
> D Proc2 PR 5P 0 >>>>>>> RSE displays as
'PROC2'
> D Parm2 D Datfmt(*ISO) Value
>
> D Proc3 PR 5P 0 Extproc('Proc3') >>>>>>>
RSE
> displays as 'Proc3'
> D Parm3 D Datfmt(*ISO) Value
>
> HTH,
> Brian.
>
>
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [4]
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 [5]
https://archive.midrange.com/wdsci-l ;.
Help support midrange.com by shopping at amazon.com with our affiliate
link: [6]
https://amazon.midrange.com ;
References
Visible links
1.
https://www.linkedin.com/in/edmundreinhardt/
2.
http://ibm.biz/rdi_hub
3.
http://ibm.biz/IBMi_ACS
4.
https://lists.midrange.com/mailman/listinfo/wdsci-l
5.
https://archive.midrange.com/wdsci-l
6.
https://amazon.midrange.com/
As an Amazon Associate we earn from qualifying purchases.