RE: Overloading in RPG.

I think it has some merits--mainly convenience, but OTOH how about using the
division operator to parse delimited strings--divisor as delimiter,
delimited string as dividend, quotient as array of parsed components.
Things could be worse.

> -----Original Message-----
> From: Gwecnal@aol.com [mailto:Gwecnal@aol.com]
> Sent: Wednesday, May 09, 2001 8:07 AM
> To: rpg400-l@midrange.com
> Subject: RE: Overloading in RPG.
> 
> 
> In a message dated Wed, 9 May 2001 07:14:08 -0500 , "Bartell, 
> Aaron L. (TC)" 
> <ALBartell@taylorcorp.com> writes:
> 
> >  Lets say that you need to calculate the due date for an 
> order that you just
> >  received, and your company calculates the due date based 
> either upon
> >  customer number or item ordered.
> 
> snip
> 
> >  Yes you could create sub procedures named
> >  #calcDueDateCust and #calcDueDateItm and I see your point 
> that it could get
> >  out of hand creating multiple sub procedures of the same 
> name.  But can you
> >  see the benefit to doing overloading if it is done right?
> 
> No I cannot.  This is a GREAT example of why NOT to do 
> overloading.  But then,
> I think a case can be made that the string concatination 
> operator should be 
> different from the addition operator, so I guess I am just odd.
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---