Re: Module source naming schemes

[bmorris@xxxxxxxxxx]

>Date: Tue, 09 Jan 2001 09:50:55 -0800
>From: Jim Langston <jimlangston@conexfreight.com>
>
>Yeah, I'm not happy with the 'F' 'N' and 'C' myself.  I am contemplating,
>and probably will, go into the //copy member for this and create some
constants.
>RNF_Open 'F'
>RNF_Next 'N'
>RNF_Close 'C'
>...
>So, all I really need to know is if it's the first time or not, and if it
is the
>first time, what the username and system name are.  Hmm.. perhaps 2 calls
then.
>
>RtvNetFIni(UserName, SysName)
>RtvNetFNxt()
> ...

Jim, using separate functions is the way I'd do it (adding a third
procedure RtvNetFClose()).  Having 3 procedures will be easier all round.
(Even if you give your callers named constants to help them get the
"which function" parameter right, there's nothing to stop them passing a
bad value, like '1' or 'n'.)

But sometimes it's easier to use parameters, and then defining constants
like you suggest is definitely the way to go.

You're right about global variables: put them in the "main source section",
before any subprocedures. These variables will be static.

Barbara Morris


+---
| 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
+---