No, it isn't, really. It's internally buffered. Most calls to getchar do not read anything, they just return a pointer to the next character in an already read buffer.
> No, it isn't, really. It's internally buffered. Most calls to getchar do not read anything, they just return a pointer to the next character in an already read buffer.
Not only that, it's permissible for getchar() to be implemented as a macro, so you might even avoid an actual function call too.
enriquto|4 years ago
lelanthran|4 years ago
Not only that, it's permissible for getchar() to be implemented as a macro, so you might even avoid an actual function call too.
OskarS|4 years ago