On Sat, Apr 11, 2009 at 01:29:23AM +1000, Matthew Palmer wrote:
> On Fri, Apr 10, 2009 at 08:06:54AM -0700, Ehren Kret wrote:
> > It builds these binary packages:
> > libgoogle-gflags-dev - a commandline flags processing library
> > libgoogle-gflags0 - a commandline flags processing library
>
> Considering the plethora of other libraries to process command line flags, I
> think you'll need to "sell" this thing a little more. What does it do that
> the competition just doesn't do? Is it needed for another package? And so
> on.
>
> - Matt
>
The distinctive feature of this library that I'm aware of is that it
allows command line flags to be defined in any file in which they're
needed and uses the linker to aggregate the flags into a single list for
parse-time.
Here's what their docs say about this:
Google's commandline flags library differs from other libraries, such
as getopt(), in that flag definitions can be scattered around the source
code, and not just listed in one place such as main(). In practice,
this means that a single source-code file will define and use flags
that are meaningful to that file. Any application that links in that
file will get the flags, and the google commandline flags library will
automatically handle that flag appropriately.
Attachment:
signature.asc
Description: Digital signature