Xref: news2.mv.net comp.os.msdos.djgpp:6023
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: a.out sections
Date: Mon, 15 Jul 1996 23:22:58 CDT
Organization: Rice University, Houston, Texas
Lines: 14
Message-ID: <31eb1922.sandmann@clio.rice.edu>
References: <Pine DOT NEB DOT 3 DOT 93 DOT 960715115844 DOT 22673A-100000 AT ananke DOT amu DOT edu DOT pl>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> That's right, but what I had in mind is creating, say, a multi-lingual
> application with support for, let's assume, 5 languages. There would be some
> fat error messages, hints, menu labels etc. Then loading it into memory at

If you use multiple sections, you will need to hand code and support a
custom stub.asm - all written in custom assembler.  Bad idea.

If you use something like DXE's (which is what they were designed for) you
can load message files dynamically - and even add new message files without
needing to re-link the main image.  You could install only the one needed 
to be even slicker.  Create an array of pointers to your messages, and
return the address of the array.

Use argv[0]'s base path to determine where to load them from.