stdio line-streaming revisited

[kris]

Andrei Alexandrescu (See Website For Email) wrote:
[snip]
> Exactly. I'm hoping to save the D community from the iostreams mess, 
> which requires the programmer to deal with two (or three as in your 
> example) incompatible APIs. 

Save the D community? The sky is not falling; no need for you to save 
anyone from anything


> It's iostreams' amazing counterperformance 
> that they managed to cut the speed so effectively in the process :o).
> 
> I think a wise thing that Tango could do is to offer a 
> backward-compatible stdio, and a high-performance I/O class using the 
> latest and greatest from each I/O (zero-copy (see 
> http://research.sun.com/techrep/1995/abstract-39.html), asynchronous, 
> threaded, kernelized, teleported, you name it).
> 
> The main desideratum is that fast/incompatible I/O is opt-in, not lock-in.

If you wish to be helpful, then let's try to forego the overt drama?

Here's an simple exercise you might indulge; let's do it in steps:

1) name every single C library that D programmers regularly use from D