Re: [abc-dev] Pass scheduling

From: Eric Bodden <>
Date: Wed, 13 Aug 2008 09:57:01 -0400

Ah, I see. Hmmm, I guess a progress bar would be nice. So feel free to
modify the code accordingly and I'd be happy to apply a patch if you
send me one.


2008/8/13 Wouter De Borger <>:
> It would, except for one little detail,
> timer (and debug) are called after each stage instead of before it,.....
> the progress bar would then constantly display the information about the
> previous stage instead of the current stage.
> The best solution is not using the progress bar at all.
> Wouter
> On Wed, Aug 13, 2008 at 3:05 PM, Eric Bodden <>
> wrote:
>> > if you think the monitor is a good idea, I'll add it to one compile
>> > sequence.
>> > but I don't know if it's worth the effort if there are many sequences
>> > (with
>> > only minor differences)
>> In the long term we would want to get rid of much of the redundancy in
>> the different versions of CompileSequence anyway. It's one of the few
>> classes in abc that's not really extensible right now - too bad that
>> you have to deal with exactly that class. I think adding calls to the
>> monitor would not hurt a lot, though (certainly not in terms of
>> performance). On the other hand it seems a bit redundant when compared
>> to the class abc.main.AbcTimer, which already exists in abc. I wonder
>> if that class is not sufficient for your needs (or an extension of it)
>> and if it would not suffice to just add a few calls to that class at
>> the places you care about.
>> Eric
>> --
>> Eric Bodden
>> Sable Research Group
>> McGill University, Montréal, Canada

Eric Bodden
Sable Research Group
McGill University, Montréal, Canada
Received on Wed Aug 13 2008 - 14:57:05 BST

This archive was generated by hypermail 2.2.0 : Fri Aug 15 2008 - 11:50:12 BST