Benjamin Peterson <benjamin at python.org> wrote: > > Can't that give you another warning about the ssize_t being truncated to > > int? > > How about the following instead? > > > > (void) write(...); > > Also, if you use a recent enough version of gcc, ./configure will > disable the warning. I would prefer if stop using these kinds of > hacks. Do you mean (void)write(...)? Many people think this is good practice, since it indicates to the reader that the return value is deliberately ignored. Stefan Krah
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4