Next: Option Descriptor File, Previous: Programmatic Interface, Up: Automated Option Processing [Contents][Index]
AutoOpts was designed to configure a program for running. This generally
happens before much real work has been started. Consequently, it is
expected to be run before multi-threaded applications have started multiple
threads. However, this is not always the case. Some applications may
need to reset and reload their running configuration, and some may use
SET_OPT_xxx() macros during processing. If you need to dynamically
change your option configuration in your multi-threaded application, it is
your responsibility to prevent all threads from accessing the option
configuration state, except the one altering the configuration.
The various accessor macros (HAVE_OPT(), etc.) do not modify state
and are safe to use in a multi-threaded application. It is safe as long
as no other thread is concurrently modifying state, of course.