[boost] Re: timer classes

From: Reid Sweatman (reids_at_[hidden])
Date: 1999-07-01 13:40:25

Not to be a pest, but personally, I'd rather see the timer and display
functionality separated.  Yes, you probably would always use the timer
functionality when using the display, but not vice versa, and I hate
dragging code into an already large codebase when I don't have to; keeps
maintenance costs down, especially since in the industry I work in, not
documenting or commenting anything seems to be the norm <g>.

> -----Original Message-----
> From: Beman Dawes [mailto:beman_at_[hidden]]
> Sent: Thursday, July 01, 1999 9:15 AM
> To: boost_at_[hidden]; boost_at_[hidden]
> Subject: [boost] Re: timer classes
> 
> 
> At 09:50 AM 7/1/99 +0000, Sean A Corfield wrote:
> 
> >Beman Dawes <beman_at_[hidden]> wrote:
> >
> >[One concern is that the message written to cout by the job_timer
> class]
> >
> >I can't believe you've tied a class to cout! The output stream
> should be a 
> >parameter (at worst) but it would be better to arrange that only the
> timing 
> >values were streamable (so the destructor writes only the value of
> elapsed() 
> >to the stream specified to the job_timer - at construction time?).
> 
> Seems like there are a couple of issues coming forward for job_timer
> and progress_display:
> 
>    1)  They are tied to cout.
>    2)  They assume non-GUI environment.
> 
> I will try to address both of these.
> 
> --Beman
> 
> --------------------------------------------------------------
> ----------
> FreeShop is the #1 place for free and trial offers and great deals!
> Try something new and discover more ways to save!
> http://clickhere.egroups.com/click/381
> 
> 
> 
> eGroups.com home: http://www.egroups.com/group/boost
> http://www.egroups.com - Simplifying group communications
> 
> 
> 
> 

------------------------------------------------------------------------

eGroups.com home: http://www.egroups.com/group/boost
http://www.egroups.com - Simplifying group communications