On 03/05/16 05:49, Sara Golemon wrote: > It's way more readable in the pipe syntax version, but it's > overloading a single statement in both places.
The rop examples show another style of working BUT it only really changes the way of ordering SOME elements of the code. And the pipe operator is only really of use in SOME areas of code? Other changes to the code base could achieve the same results, such as creating the 'improved' array handling API that people keep calling for? I accept that parameter ordering on some functions is not the best for streamlining some steps, but even pipe chaining has it's restrictions and so again is not a total solution, simply another 'complication' when trying to read code. I still think this fails to understand the complexity it adds to handling changes to the code as/if other variations of intermediate code handling ARE required. As I said previously, pulling PDO chaining apart tends to be the first step to correct code that is ignoring intermediate errors, and simply trying to 'chain' all of the errors together via exceptions does not work ... as demonstrated in the rop demonstrations which HAVE to break out exceptions to make the flow work. -- 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
