Remove InterruptibleProcessor and Rename FingersCrossedProcessor about pipeline HOT 3 CLOSED

@GreatOwl sorry for the (very) late response. First of all, thank you for the comments. I've thought quite some time how such a component should be named. I went with "fingers crossed" mostly because Monolog has a similar handler type, which I thought was kind of funny. I also like the fact that you almost feel like you should think about what happens when things don't go according to plan, like a try/catch block around the execution. However, I am totally open to suggestions. Names like DefaultProcessor don't really cover the load because it doesn't describe what that kind of processor does. With "fingers crossed" you can assume there's no error handling or checks involved, which is something I like about that name.

from pipeline.

I think that is a fair assessment of your decision.

From my position I see the opportunity for being able to apply a functional pattern with this library, modifying state as each stage completes. The original implementation was wonderful in my opinion because of its use of top level functions instead of a foreach during execution.

The usage of the foreach is logical however for those dealing with a traditional stack, and gathers no opposition.

so I will willingly close this, and request your continued attention to:
#24

Thanks @frankdejonge

from pipeline.

@GreatOwl converting the array_reduce into a foreach was unfortunate, but PHP's handling of exceptions was nipping it in the butt. When an exception is thrown it's unrecoverable unless handled inside the stage, which is not always desired. This made me have to "downgrade" the actual implementation, I share your grief.

from pipeline.