Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2001:
[Freeciv-Dev] Re: GUI-specific options don't work properly in 1.12.0 (PR
Home

[Freeciv-Dev] Re: GUI-specific options don't work properly in 1.12.0 (PR

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Kevin Brown <kevin@xxxxxxxxxxxxxx>
Cc: Vasco Alexandre Da Silva Costa <vasc@xxxxxxxxxxxxxx>, freeciv-dev@xxxxxxxxxxx, bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: GUI-specific options don't work properly in 1.12.0 (PR#892)
From: Andreas Kemnade <akemnade@xxxxxxxxxxx>
Date: Sun, 12 Aug 2001 20:50:00 +0200

Kevin Brown writes:
 > Vasco Alexandre Da Silva Costa <vasc@xxxxxxxxxxxxxx> wrote:
 > > On Sun, 12 Aug 2001, Kevin Brown wrote:
 > 
 > [...]
 > 
 > > > My question is: why are we using our own option parsing functions,
 > > > instead of using getopt() and friends?
 > > 
 > > Search the mailing-list archives.
 > 
 > A good idea.  But it unfortunately proved to be a completely useless
 > exercise (and yes, I searched ALL of the archives).  The only hit I
 > got that suggested any problems with getopt was a patch to take it out
 > of the gtk client due to bugs in GNU getopt (which I would expect have
 > been fixed by now!).  Everything else referred to a comment that
 > reads:
 > 
 >  /* no  we don't use GNU's getopt or even the "standard" getopt */
 >  /* yes we do have reasons ;)                                   */
 > 
 > 
 > Anyone have any historical insight into the reasons we don't use
 > getopt?
I think there are portability problems. Not every platform freeciv is
compiled for has getopt (windows, amigaos, etc.). As far as I can
remember getopt is not very portable. But maybe that has changed.

Greetings
Andreas Kemnade


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