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: Vasco Alexandre Da Silva Costa <vasc@xxxxxxxxxxxxxx>
Cc: freeciv-dev@xxxxxxxxxxx, bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: GUI-specific options don't work properly in 1.12.0 (PR#892)
From: Kevin Brown <kevin@xxxxxxxxxxxxxx>
Date: Sun, 12 Aug 2001 10:38:07 -0700

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?



-- 
Kevin Brown                                           kevin@xxxxxxxxxxxxxx

    It's really hard to define what "unexpected behavior" means when you're
                       talking about Windows.


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