'Albrecht Schlosser' via fltk.coredev wrote:
> 
> [...]
> More info:
> 
> - According to the POSIX man page [2] for putchar(int c) "The function
> call /putchar/(/c/) shall be equivalent to /putc/(/c/,/stdout/)."
> - According to the POSIX man page [3] for putc(int c, FILE *stream) "The
> /putc/() function shall be equivalent to /fputc/()
> <https://pubs.opengroup.org/onlinepubs/9699919799/functions/fputc.html>,
> except that if it is implemented as a macro ..."
> 
> Honestly, I don't read this as "putchar() can be implemented as a macro"
> (emphasis on "The */function/* call /putchar/(/c/) ..." in the docs) but
> as it stands, on the tested system putchar **is** defined as a macro.

There are other Unix systems that seems to intentionally provide a
macro for putchar() and document it.

IBM documentation for AIX:
<https://www.ibm.com/docs/en/aix/7.2?topic=p-putc-putchar-fputc-putw-subroutine>
| 
| The putchar macro is the same as the putc macro except that
| putchar writes to the standard output.

Oracle documentation for Solaris:
<https://docs.oracle.com/cd/E88353_01/html/E37843/putchar-3c.html>
| 
| The call putchar(c) is equivalent to putc(c, stdout).
| The putchar() routine is implemented as a macro.

-- 
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/20240327110221.22ab6c8f%40WStation5.stz-e.de.