possible open() problem again

[Denis Leroy]

Jakub Jelinek wrote:
> On Thu, Aug 23, 2007 at 09:36:31PM +0100, Ian Chapman wrote:
>> <snip>
>> int open(const char *pathname, int flags, ...)
> 
> When it defines its own open implementation, you should just
> prevent expanding it as function-like macro.
> So
> int (open)(const char *pathname, int flags, ...)
> {
> ...
> }

I can't help but cringe at this horrible open() macro hack we have to 
deal with now. I mean, this was perfectly legal C code and we can't 
compile it ?!