Re: Weirdness in comm(1)

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Tue, Dec 01, 2009 at 01:17:45AM +0000, Roy Marples wrote:
> Is there a reason that it's exposed to userland anyway?
> If not, we could just #define it as void * for non libc.
> That would allow for any future changes to its internals.

A bunch of broken programs depend on being able to look into the
internals. There is also the issue that e.g. getc is often used in the
tight inner loops and shouldn't have function call overhead without good
reasons.

Joerg