http://d.puremagic.com/issues/show_bug.cgi?id=10344
--- Comment #12 from Steven Schveighoffer <[email protected]> 2013-06-17 13:21:02 PDT --- (In reply to comment #11) > The program has made a decision that assumes writes to stdout, if any, have > succeeded. You seem to be ignoring the use case. The return code is based on database update success, not stdout success. In fact, I can write the code in such a way that specifically ignores stdout failures, yet still have this come up. > > Consider the case where the filesystem driver fails to finish writing the > > file > > after the program exits. How do we handle that? > > That is not under our control. None of this is under our control. It's outside our visibility. But the effect is the same -- data is not written. We can't say definitively that a D program guarantees the data goes to it's final destination. The error is in fact useless because success doesn't guarantee the write occurs. In fact, all a success guarantees is that the program succeeded according to it's charter. I have another compromise that I will post to this bug report separately. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
