I think that flushing the output more often should not be an option. Flushing in this case is cheap and prevents stream readers (another process or a text file) from staying outdated...
On Mon, Sep 14, 2009 at 11:03 AM, Hart, William E <[email protected]> wrote: > Hi, Andrew. > > By default, IO streams are not regularly flushed; they are buffered in the > computer until 'enough' IO has been done (or until the stream is closed). > > I'm piping glpsol through some Python code and this buffering is creating a > noticable delay in my processing. What I'd like is an option that enables > explicit flushing of glpsol's output. For example, after each status line > is printed, you might execute: > > flush(stdout) > > (or do "cout << flush" in C++). > > --Bill > > > -----Original Message----- > > From: Andrew Makhorin [mailto:[email protected]] > > Sent: Sunday, September 13, 2009 5:27 PM > > To: Hart, William E > > Cc: [email protected] > > Subject: Re: [Help-glpk] Feature request - option to flush output > > > > > I'd like to see an option in GLPK that allows the output > > summary to be > > > flushed on a regular basis. I understand why you might leave this > > > 'off' by default, but allowing users to have very active > > updates adds > > > some value to their interactions with GLPK. > > > > Could you please clarify your request in more details? Thanks. > > > > > > Andrew Makhorin > > > > > > > > > > > > _______________________________________________ > Help-glpk mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/help-glpk > -- ============================================================= Haroldo Gambini Santos Computing Department - Universidade Federal de Ouro Preto - UFOP email: [email protected] home/research page: http://www.decom.ufop.br/prof/haroldo/ “BE the change you want to see in the world” -Mahatma Gandhi
_______________________________________________ Help-glpk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-glpk
