gnunet-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] Are getopt.c getopt1.c sequencer.c ever used ?


From: Blake Matheny
Subject: Re: [GNUnet-developers] Are getopt.c getopt1.c sequencer.c ever used ?
Date: Tue, 14 May 2002 02:21:14 -0500
User-agent: Mutt/1.3.99i

The getopt stuff is included for two main reasons. First, only
the GNU implementation of getopt() has getopt_long() and second,
not every non-gnu implementation of getopt handles getopt()
options the same way. For example, on BSD you have to install the
gnugetopt library if we didn't include the files. On solaris,
the handling of optind/optarg is broken/different then gnu. By
including the GNU implementation of it we are assured that GNUnet
can truly be easily ported to new platforms, and that's one less
area to look for bugs. So yes, we are likely to run across such a
library :-) I'm not sure about src/util/sequencer.c, as none of
its functions are called by any other piece of code. Christian?

-Blake

Whatchu talkin' 'bout, Willis?
> Im just wading through the files, in ./src/util there are a few files that
> dont appear to be used.
> 
> I assume getopt.c and getopt1.c must be provided to enable compiling
> against c libraries that dont have getopt included, but are we likely to
> run across such a c library ?
> 
> Is src/util/sequencer.c an old unused file, or is it for future work ?
> 
> 
> Glenn
> 
> _______________________________________________
> GNUnet-developers mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gnunet-developers

-- 
Blake Matheny
address@hidden
PGP-Key http://www.dbaseiv.net/purdue.key



reply via email to

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