Date: Tue, 10 Mar 1998 10:57:57 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Esa DOT Peuha AT Helsinki DOT FI
cc: djgpp AT delorie DOT com
Subject: Re: Anyone running on Win95 or NT?
In-Reply-To: <Pine.OSF.3.96.980310090037.10939A-100000@vesuri.Helsinki.FI>
Message-ID: <Pine.SUN.3.91.980310105039.3898O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 10 Mar 1998, Esa A E Peuha wrote:

> Do you mean header files generated by the configuration process?

Yes.

> But even
> then I don't really see the problem. A piece of djgpp-specific code can
> get the value of DJDIR at startup (and use "c:/djgpp" if DJDIR is not
> set), and then concatenate it with relative paths into global arrays which
> can then be used like the header-defined fixed strings. Am I missing
> something here?

The problem is that code which references such constant path names is not
localized enough.  I cannot afford to list here every way in which
constant strings can be used whereas non-constant cannot; I suggest
looking into the packages, if you are really interested.  One example is
when the configuration process generates a header with lines like this: 

	#define DEFAULT_FOO_PATH "/usr/local/share/foo"

(with the "/usr/local" being replaced by whatever is specified during the 
configure step), then uses these macros in many places in the source.