Re: Function Opinion

["Keith Carpenter" <CarpCon@xxxxxxx>]

Single module service programs won't avoid signature issues.

Signatures are not based on the number of modules in service program, but
instead the name, number and order of functions/data exported.   If you add
an exported function to a single module service program you'll still get a
different signature (assuming no binder source).

Actually, the single function approach avoids the signature issue. But as
most here are concurring, it's really not very practical.

Binder source is actually a good thing.  It allows you to version the
service program with multiple signatures.


Keith



----- Original Message ----- 
From: "Johnson, Duane" <djohnson@xxxxxxxxxxxxx>
To: "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, October 15, 2003 8:28 AM
Subject: RE: Function Opinion


>   Oh, Thank you very much.
>   I prefer to use one module per service program.  Maintenance is greatly
> simplified, I can use a binding directory (one per program) to define all
> the modules and service programs used, and I NEVER have to worry about
> binder language, signatures, etc.
>
> Duane
>
> -----Original Message-----
> From: Bob cozzi [mailto:cozzi@xxxxxxxxx]
> Sent: Wednesday, October 15, 2003 9:37 AM
> To: 'RPG programming on the AS400 / iSeries'
> Subject: RE: Function Opinion
>
> That has to be the dumbest thing I have ever heard of with regards to
> Service Program design.
> Bob Cozzi
> Cozzi Consulting
> www.rpgiv.com
>
>
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>