Re: Statically binding multiple MAIN modules with display files

[James Rich <james@xxxxxxxxxxx>]

On Tue, 20 Jan 2004, Joe Pluta wrote:

> Is there a good reason to bind together multiple application programs
> each with their own display files, or is the recommendation still to use
> dynamic CALLs?
>
> What are the pros and cons of binding multiple programs together that
> have their own display files?  It seems to me that this is a place where
> the dynamic CALL still makes sense.

Hmm... I guess I am under the mistaken impression that you can't bind
multiple MAIN modules together?  I always understood that a single program
object (which is what results after binding the modules) can only have one
MAIN procedure.

We use modules that have their own display files.  We usually have them
defined as USROPN.  Our most common case is a modules which asks the user
to verify that they want to discard or save changes before exiting a
program.  The module (which is NOMAIN) has its own display file.  We've
never had a problem and it is really nice.

But perhaps I'm talking about something different than what you are
asking?

James Rich

"As for security, being lectured by Microsoft is like receiving wise words
on the subject of compassion from Stalin."
      -- mormop on lwn.net