On 03/05/16 19:57, Sara Golemon wrote: > Intermediate variables also add cognitive overhead of their own in > cataloging all the various intermediates used in a large function. By > removing the explicit intermediate variables and replacing them with > unnamed temporaries, the code becomes easier to read because there's > less unnecessary assignments cluttering up the space.
Doesn't this assume that you understand just what each stage of the pipeline is returning? Part of the criticism of PHP is that functions are not consistent, so do you end up with a list of functions that can be used and a list that can't? The returns are not what the pipeline is handling? I can understand the advantage of making a consistent interface but as we all understand, that has to co-exist with the current procedural one. https://github.com/nikic/scalar_objects is another attempt at supporting a different style of working which looks a lot more practical than continuing to shoehorn bits into the 'old style' API? -- 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
