You could very well use a return value instead of, or in addition to,
the MyDate field on the JoinDate(). That would indeed let you use it in
an expression. I threw that together quickly and just tried to use the
same syntax for each function.
Const would be an alternative. I was just casting the "whatever" data
type to a known int.
Since multiple values need to be updated, I'd just modify the incoming
parms instead of doing 3 calls. It just seems second nature since I've
always done it that way in C.
Paul.Nicolay@xxxxxxxxxx 01/12/2010 2:52:05 PM >>>
Roger,
Why wouldn't you use a result field for JoinDate ? Even for functions
as SplitDate I use return values (and provide a parameter that tells me
what to extract which indeed results in 3 function calls instead of one,
but as far as I'm concerned it's much cleaner code).
If you now need this in an expression, you first need to store it in a
variable.
And why those %int ? Just define the parameters as "10I 0 Const" and
there's no need to use the %int.
Kind regards,
Paul
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Harman
Sent: dinsdag 12 januari 2010 22:14
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: RPG overloading (was RPGV?)
I did miss that. I'm assuming that MyDate is a real date field or, at
least, always the same type??
What about....
JoinDate( MyDate : %int(myYear) : : %int(myMonth) : %int(myDay);
I'd still do SplitDate() with integer components. If you need to change
them after the fact, just deal with that.
Two procedures....
midrange.com
