On 6/14/2013 12:10 AM, Jacob Carlborg wrote:
On 2013-06-13 20:11, Walter Bright wrote:
I know it isn't hard. But D's charter is not to go and patch the C
runtime library, nor is that remotely practical across all the thousands
of C implementations out there.
Why not? Why shouldn't we try to be better than C? Perhaps we shouldn't rely on
the C runtime library in this case, if possible.
That behavior is normal to anyone used to working with C stdio.
But we're using D here, not C. You have to stop assume that everyone using D
knows C or C++. Just because you do doesn't mean everyone else does.
D is set up to work hand-in-glove with C. This isn't going to change, as such
compatibility is a big feature of D.
Part of that is seamlessly working with existing C I/O. D code that does
writeln's interleaved with C code that does printf's should work as expected.
Since this particular issue can be easily fixed without "fixing" the C runtime,
there is no motivation to do so, either.
