On 6/12/13 2:36 PM, Steven Schveighoffer wrote:
On Wed, 12 Jun 2013 11:56:59 -0400, Walter Bright
<newshou...@digitalmars.com> wrote:
On 6/12/2013 8:34 AM, Steven Schveighoffer wrote:
On Wed, 12 Jun 2013 11:32:58 -0400, Andrei Alexandrescu
<seewebsiteforem...@erdani.org> wrote:
I agree performance is not a problem. But it's just weird behavior.
We should
flush stdout termination, anything else would have to be carefully
justified -
and this is not.
stdout is flushed on termination. Your code just doesn't puke a stack
trace if
there is an issue after main exits.
There is main(), and then there is _Dmain(). Take a look at
druntime/src/rt/dmain2.d
I don't get the point.
Upon process termination, the C runtime flushes stdout/stderr.
There is no reason to reinvent this wheel.
Flushes but doesn't propagate the potential error to the return code.
Let's take further discussion to
http://d.puremagic.com/issues/show_bug.cgi?id=10344. I think what we
need to do is cut and dried.
Andrei
