On Fri, 2009-04-10 at 08:52 -0700, Ehren Kret wrote: > On Sat, Apr 11, 2009 at 01:29:23AM +1000, Matthew Palmer wrote: > 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. Hardly distinctive, I wrote that in libgetopt++ in (checks changelog) 2002. -Rob
Attachment:
signature.asc
Description: This is a digitally signed message part