On 30/04/16 16:03, rich gray wrote: >> As I said in the message ... no problem if you simply have a SINGLE >> pathway through the code. That video simply assumes that anything that >> is not success is an error. MUCH of my code base has turntables or three >> way switches which in addition to possible errors, you have a lot more >> than one 'success' output. >> > If it doesn't suit your code base design then simply don't use the > feature ... I don't see the need for you to raise objections here simply > because it doesn't fit your purposes..
The problem is not with ME using this sort of re-factoring of code, it's managing and maintaining code others have 'improved' but applying it. I have a similar problem with chained operators in classes like PDO. Invariably the 'edge cases' where nothing is returned at a point in the chain are not handled or throw an exception, where ACTUALLY you want to process the 'mid point' of the chain and create a split in the flow. Someone having tidied what was perhaps nicely documented and structured code into the one single chain may not be the right thing when missing elements need to be added to the workflow. Having now watched more of the linked talk I find the one thing that I do like with that model ... trap exceptions and put them back into the workflow ... The second half of the video is well worth watching! I like the idea that you keep the action open to do retries such as resending the email if it failed first time. That is not a simple exception on the workflow of a pipe operation but is a major difference between compiled languages and scripting process. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
