ARGP: Documentation of

2014-12-03 Thread Robert Hairgrove
Hello, I am writing some little C++ wrapper classes for the argp functions. Unfortunately, I cannot find any documentation of the argp_child::flags member, i.e.: what possible values it could have. The only documentation seems to be the one line comment in argp.h: "Flags for this child", which is

Re: ARGP: Documentation of

2014-12-04 Thread Robert Hairgrove
Robert Hairgrove roberthairgrove.com> writes: > I am writing some little C++ wrapper classes for the argp functions. > Unfortunately, I cannot find any documentation of the argp_child::flags > member, i.e.: what possible values it could have. The only documentation > seems to

Re: ARGP: Documentation of

2014-12-05 Thread Robert Hairgrove
Robert Hairgrove roberthairgrove.com> writes: > Robert Hairgrove roberthairgrove.com> writes: > > I am writing some little C++ wrapper classes for the argp functions. ... One more question: If argp_parse calls exit() and terminates the program, will the destructors of my C++ ob

Re: ARGP: Documentation of

2014-12-05 Thread Robert Hairgrove
Robert Hairgrove roberthairgrove.com> writes: > If argp_parse calls exit() and terminates the program, will the destructors > of my C++ objects be called? Silly question ... now I realize that they won't be called unless I take appropriate precautions, such as keeping a gl

ARGP: Recent versions do not define OPTION_NO_TRANS

2014-12-12 Thread Robert Hairgrove
Using glibc-2.15, the copyright notice in argp.h goes up to 2009, yet the symbol OPTION_NO_TRANS is not defined there (and presumably not processed by any of the argp code). Was this removed again sometime later? Please refer to this patch from 2004 for details: http://lists.gnu.org/archive/html/

Re: ARGP: Recent versions do not define OPTION_NO_TRANS

2014-12-12 Thread Robert Hairgrove
Eric Blake redhat.com> writes: > > On 12/12/2014 05:08 AM, Robert Hairgrove wrote: > > Using glibc-2.15, the copyright notice in argp.h goes up to 2009, yet the > > symbol OPTION_NO_TRANS is not defined there (and presumably not processed by > > any of the argp code)