Complete.Org: Mailing Lists: Archives: freeciv-dev: January 2002:
[Freeciv-Dev] Re: PATH_SEPARATOR
Home

[Freeciv-Dev] Re: PATH_SEPARATOR

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Alexander Mai <st002279@xxxxxxxxxxxxxxxxxxxxxx>
Cc: "freeciv-dev@xxxxxxxxxxx" <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: PATH_SEPARATOR
From: Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 30 Jan 2002 13:43:50 +0100
Reply-to: rf13@xxxxxxxxxxxxxxxxxxxxxx

On Wed, Jan 30, 2002 at 11:55:40AM +0100, Alexander Mai wrote:
> Hello,
> 
> I have a question regarding PATH_SEPARATOR:
> The ChangeLog says:
>       * acconfig.h, config.h.in, common/shared.c: Allow manual config.h
>       to define PATH_SEPARATOR to specify the separater to be used in
>       the freeciv data path (FREECIV_PATH).  If this is not defined (and
>       configure does not do so), falls back to using colon. 
> 
> Shouldn't one have either a configure check or explicit 
> catches for systems which don't use ':'?
> 
> shared.c could look like:
> 
> /* If no path separator is defined use colon */
> #ifndef PATH_SEPARATOR
> #ifndef __EMX__
> #define PATH_SEPARATOR ";"
> #else
> #define PATH_SEPARATOR ":"
> #endif
> #endif

Or like intl/loadinfo.h:

/* Separator in PATH like lists of pathnames.  */
#if defined _WIN32 || defined __WIN32__ || defined __EMX__ || defined __DJGPP__
  /* Win32, OS/2, DOS */
# define PATH_SEPARATOR ';'
#else
  /* Unix */
# define PATH_SEPARATOR ':'
#endif

> BTW, the ChangeLog is quite old, it is not updated regularly in CVS?

It will be updated for the release.

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
 "The two rules for success in life are:
  1) Never tell them everything you know."


[Prev in Thread] Current Thread [Next in Thread]