On 13/07/11 08:55, Joachim Schmitz wrote: > I found this in mktemp.c, line344 (well, my compiler found it for me and > warned about 'possible use of "=" where "==" was intended'): > > if (!dry_run && (stdout_closed = true) && close_stream (stdout) != 0) > > Not sure whether this is bug or feature ;-)
Well it's a feature. We could reorganize but it would add a few more lines. What compiler (option) is this? Is the warning avoided by using double brackets like ((stdout_closed = true)) cheers, Pádraig.
