RE: when to use a function or file for information

["Evan Harris" <spanner@xxxxxxxxxx>]

Don't you see any resemblance to a *table* there at all ?

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Wednesday, 24 March 2010 8:10 p.m.
To: Midrange Systems Technical Discussion
Subject: RE: when to use a function or file for information

> -----Message d'origine-----
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Loyd Goodbar
>
> Like Jonathan said, if you can infer the flag, just put that 
> in a subprocedure and be done with it.

So, if the flag were dependent upon say, the client type, I could have :

clientFlag = getClientFlag ( clientType )

and in getClientFlag :

 If clientType = TYPE_THIS....etc
 If clientType = TYPE_THAT....etc

But this is seen as 'hard-coding' the client type and seems to be
discouraged here. Hence the preference for adding the flag to the client
file.