Re: Handling 'initializer element not constant' error

viza wrote:
) Hi
)
) On May 7, 3:14 pm, Gowtham <gowthamgowt...@[EMAIL PROTECTED]
> wrote:
)
)> I had some C code written which initialized a global variable as:
)>
)> FILE *yyerfp = stdout;
)> ...
)> But, this code will also be compiled into a shared object
)> ...
)> What is the best way of solving this problem?
)
) The correct and best way to solve this problem is to remember that
) library functions should not write to the standard streams.
)
) Imagine that stdin, stdout and stderr are local variables within
) main().  Any library function that needs to write to a file should
) take a pointer to one as an argument.  The author of main() can then
) pass stdout *if* they give you permission to write to it.
)
) This makes your code more modular and easier to reuse, it makes it
) easier to read and debug because you can follow information flow from
) the prototypes only, and it also stops developers who use your library
) from pulling their hair out because you are printing to streams that
) you shouldn't, not following their message conventions or corrupting
) their output completely.

There was a discussion recently where someone was trying all kinds of
hacks
and workarounds to capture the output from a library, because he did not
want it to go to stdout.  

I would consider that a very good example of why your advice is good
advice.  To the OP: libraries shouldn't be using stdout, and certainly
not hardwired.


SaSW, Willem
-- 
Disclaimer: I am in no way responsible for any of the statements
            made in the above text. For all I know I might be
            drugged or something..
            No I'm not paranoid. You all think I'm paranoid, don't you !
#EOT