Hi,
If I call the procedure as follows...
s = MyProc(%SubSt(s: 1));
... it works fine. This forces the conversion due to the expression, but I'm still wondering if the compiler shouldn't do the same when he notices that I pass a Varying(2) while a Varying(4) is expected ?
Kind regards,
Paul
________________________________
From: rpg400-l-bounces@xxxxxxxxxxxx [rpg400-l-bounces@xxxxxxxxxxxx] on behalf of Paul Nicolay [Paul.Nicolay@xxxxxxxxxx]
Sent: Wednesday, April 13, 2011 11:41
To: rpg400-l@xxxxxxxxxxxx
Subject: Varying(4) bug ?
Hi,
I'm introducing Varying(4) into my programs as I need to handle more data, but I'm experiencing something strange.
I have a procedure that accepts a Varying(4) which is defined with the Const keyword. If I now call this procedure, passing a normal Varying... the first two bytes of the string itself are dumped in position 3 and 4 of the Varying(4) field ? See dump data below, ie. the "He" or x'C885' gets into byte 3 and 4 ?
Shouldn't "Const" not solve this issue ?
Example:
H DftActGrp(*No) ActGrp(*Caller)
DMyProc PR 100 Varying(4)
D Var4 100 Varying(4) Const
Ds S 100 Varying
/free
s = 'Hello world.';
s = MyProc(s);
*INLR = *On;
Return;
/end-free
**********************************
* MyProc *
**********************************
PMyProc B Export
DMyProc PI 100 Varying(4)
D Var4 100 Varying(4) Const
**********************************
* Main *
**********************************
/free
// Dump 000CC885 93939640 A6969993 844B0000 - ..Hello world...
Return Var4;
/end-free
P E
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/rpg400-l.
midrange.com
