overloading with RPG is not possible.
You may get your function overloaded if you register 2 different RPG
functions as SQL UDFs with the same name.
Contrary to RPG SQL UDFs can be overloaded.
But calling a RPG function via SQL UDF from within RPG will be the reverse
Mit freundlichen Grüßen / Best regards
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and loosing them? Not training them
and keeping them!"
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von tim
Gesendet: Friday, 29. August 2008 20:03
An: 'RPG programming on the AS400 / iSeries'
Betreff: RE: passing char/num variable to a subproc question
Im using this technique, but wanted to know if we had a neat way of doing it
(can you say overloading Aaron)
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of DeLong, Eric
Sent: Friday, August 29, 2008 1:11 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: passing char/num variable to a subproc question
Not directly... You simply use a bif to convert your numerics to character.
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of tim
Sent: Friday, August 29, 2008 11:54 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: passing char/num variable to a subproc question
I have a the following coded subproc:
P WriteDiff b
D WriteDiff pi
7d fieldchange 10 const
d value 80 const
lgfldch = fieldchange;
lgvalue = %trim(value);
P WriteDiff e
Is there a way to do this that no matter if I pass a character or numeric
defined field, the subproc would work.
So, both of these would work.
D NUMBER 10S 0
D TEXT 20
Writediff('number' : number);
Writediff('Text' : text);
I am thinking that I would pass a pointer rather then the value, but not
sure how I would code this.
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact