RE: It's That Time Again! The 2002 RPG Enhancement Poll

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Bartell, Aaron L. (TC)
>
> I would like to be able to do this:
>
> eval custDescription = CUSTOMER.getDescription(1234)
> eval itemDescription = ITEM.getDescription('HAT')

Aaron, this is a great concept.  Combine this with procedure overloading
based on parameters, and you've extended the RPG name space tremendously,
and made it possible to start writing service programs from templates.  For
example, every service program could have read, write, update and delete
procedures - you'd just change the implementation for each one.  Programmers
would then know that to get a given business object, they simply execute the
read procedure from the appropriate service program.

I'm not trying to go OO here.  As has been discussed, you can do a lot of
that with procedure pointers if you really need to.  But having a common,
consistent naming convention across service programs is really a biggie.

Joe