Maybe we should just stick with compile-time modularity :-D (did I just suggest we make tons of macros?)

 */

struct options_common

{

  struct options_common_data *data;

  struct remoteio_opts *remoteio;

  struct client_opts *client;

  struct daemon_opts *daemon;

};

/**

  This function needs to eat some of your arguments to it, just like gtk+ and other libs like to. It particularly needs to be able to find the location of the config file, which should be taken from arguments if it's there. The argument list will have members that I recognize removed.

  Options should be kept alive during the program's life.

  \param mycfg will be set to the section of the configuration file specific to the caller (client or server specific section)

  \param myopts holds the caller's confuse option declarations

  \param myname holds the name of the section of the config file that refers to mycfg and myopts

  \param allopts will be set to a pointer that many functions need for operation

  \param argc the argc that was passed to main()

  \param argv the argv that was passed to main()

 */

int options_init(int argc, char *argv[], cfg_t **mycfg, cfg_opt_t *myopts, char *myname, struct options_common **allopts);