[llvm-dev] Why does LLVm 3.8.0 recognize fputs_unlocked as a vararg function?

[Tim Northover via llvm-dev]

On 27 October 2017 at 11:01, Dipanjan Das via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Can anybody explain why fputs_unlocked() is recognized as a vararg method
> while it accepts two fixed parameters?

Are you sure the correct header has been included? Without that
declaration the legacy C rules dictate essentially that prototype.
Clang ought to give a warning about it though.

Tim.