[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-glpk] Feature request - option to flush output

From: Haroldo Santos
Subject: Re: [Help-glpk] Feature request - option to flush output
Date: Mon, 14 Sep 2009 11:21:47 -0300

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 <address@hidden> 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:


(or do "cout << flush" in C++).


> -----Original Message-----
> From: Andrew Makhorin [mailto:address@hidden]
> Sent: Sunday, September 13, 2009 5:27 PM
> To: Hart, William E
> Cc: address@hidden
> 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

Haroldo Gambini Santos
Computing Department - Universidade Federal de Ouro Preto - UFOP
email: address@hidden
home/research page:

“BE the change you want to see in the world” -Mahatma Gandhi

reply via email to

[Prev in Thread] Current Thread [Next in Thread]