Re: Handling 'initializer element not constant' error

> Assuming the OP can change the code of the library, he could
> initialise yyerfp to NULL and replace all the uses of it with
>
>    (yyerfp ? yyerfp : stdout)
>
> It's a pity there isn't a standard way to get initialisation code run.
>
> -- Richard

I'd mention here a few more poins:
- <OFF>The OP want's to initialise his shared library
       (although he could avoid it with a different design). [he can
be she]
       This is usally possible on a decent operating system by
defining
       a function with a magic name.
  </OFF>
- Global objects are not quite unusual animals (especially if they are
constant)
  and one can design them using e.g. a variant of the singleton
pattern.
  In C that would be to define a pointer-to-function, and one can
indeed initialise that
  to an other function. In this case:

  FILE *yyerrf_default() { return stdout; }
  static FILE *yyerrf_ptr;
  FILE *yyerrf_user() { return yyerrf_ptr; }
  FILE *(*yyerrf)()=yyerrf_default;
  void yyerrf_set(FILE *F) { yyerrf_ptr=F; yyerrf=yyerrf_user; }
  #define yyerrf yyerrf() // protected // don't yell // is legal in
c99
  #define yyerrf_ptr      // protected

  (This is a slightly overcomplicated singleton, but of some
unjustified reasons I avoid conditionals.)

Szabolcs