<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Consolas'; font-size:11pt; font-weight:400; font-style:normal;">On Friday 06 February 2009, David Faure wrote:<br>
> On Tuesday 20 January 2009, Thiago Macieira wrote:<br>
> > The problem with buffered mode is that write() will report that it wrote<br>
> > all bytes, but the saving of them to disk might fail. In that case, the<br>
> > write happens inside flush()<br>
><br>
> So a solution is to test the return value of flush(), right? That's<br>
> actually easier than checking each and every write() call... (and much more<br>
> performant than using Unbuffered).<br>
><br>
> When does flush happen if not called explicitely? In close? So we should do<br>
> this?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>There's no guarantee that in buffered mode write() won't actually have to write to disk though, is there? We know that pending changes will have been written out by flush() but there's no reason that write() won't actually write if its own internal buffers fill up.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Regards,<br>
- Michael Pyne</p></body></html>