[En-Nut-Discussion] Why does the internal libc defines a _write() and _read() instead of write() and read()?

Ole Reinhardt ole.reinhardt at embedded-it.de
Tue Sep 29 23:27:04 CEST 2015

Hi all,

I just wondered, why the Nut/OS implementation of write() and read() is
called _write() and _read()?

Likely this was a decision due to a name conflict with some other
library implementations, but I'd like to know the background.

Best regards,


kernel concepts GmbH            Tel: +49-271-771091-14
Sieghuetter Hauptweg 48         Mob: +49-177-7420433
D-57072 Siegen

More information about the En-Nut-Discussion mailing list