Re: function with a bunch of parameters

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

David

Alan's comment included the problem of many parameters that change a lot 
- not just many parameters. There's really nothing wrong with having 
several parameters to pass the information you need in the procedure or 
program being called.

You also are limited by all those RPGIII programs - which are probably 
not going to change anytime soon. So you cannot return values - 
everything has to be in parameters. Wait - if this is a new program, 
don't the consuming programs have to be changed, as well? Are you 
restricted to using RPGIII? Can you go to ILE?

Hope my questions are on point - good luck
Vern

David FOXWELL wrote:
> Hi all,
>
> When I first discovered this list, I started a discussion that made Alan Campin's stomach turn. It was remembering these last two words that helped me refind the discussion in the archives.
>
> I was particularly impressed by Alan's response here : http://archive.midrange.com/rpg400-l/200706/msg00363.html
>
> I've kept that in mind ever since and I'm sure that my programs have improved because of this approach. However, I've just been given a function to write where the parameters are already given for me. Alarm bells are ringing.
>
> Here's my list of parameters
>
> Input
>
>     Product code
>     Date (to see if the tax was applied at that time )
>     Cost before taxes
>
> Output
>
>     Cost with all taxes applied
>       Total of all different taxes
>     MODS details of  each tax applied:
>         Tax code
>         Tax type
>         Tax rate (%)
>         Tax total (EUR)
>
>
> I'd be interested to know how you'd  go about reducing the size of this bunch of parameters. A lot of RPG400 will need this information.
>
>