Re: [Babeldoc-devel] PipelineStageFactory

[Bruce M. <br...@mc...>]

Erik, all,

Comments inline.

On Tuesday 22 April 2003 09:56 am, ek...@ba... wrote:
> <<
> It can be explained by not having your set of requirements at the time of
> writing.   You will probably need to implement the changes you need
> yourself.
>
>
> Understood.  Not a problem.
>
> So, shall I implement these changes in the codebase or do I need to
> diverge from the codebase at this point in time?

No, dont fork the codebase, let the exceptions move up the stack - just make 
sure that they get caught "somewhere".  The "somewhere" in the case of 
PipelineFeeder.process is ultimately called from PipelineFeeder.execute.  In 
this case all the possible exceptions are caught so all is well. 

> Note: I suspect we may find things that "break" once the exceptions start
> flowing through the call stack.

This is probably a good thing - we will need to fix theses places.

> Additionally, I'm sure there are a few truly legitimate places where the
> exceptions are not important and processing handles this.  If there is any
> insight into examples of these, please advise.

Lets deal with that when we find them.  Sorry to be not specific.

> Erik
>
> ________________________________________________________________________
> The information in this e-mail, and any attachment therein, is confidential
> and for use by the addressee only. If you are not the intended recipient,
> please return the e-mail to the sender and delete it from your computer.
> Although The Bank of New York attempts to sweep e-mail and attachments for
> viruses, it does not guarantee that either are virus-free and accepts no
> liability for any damage sustained as a result of viruses.