On 06 Feb 2012 at 07:47, Adam Richardson <simples...@gmail.com> wrote:
> While not purely focused on PHP, I toss this out to the group because I > believe there are some novel, interesting points regarding the potential > benefits of using the goto construct as implemented in PHP: > > http://adamjonrichardson.com/2012/02/06/long-live-the-goto-statement/ Your val_nested() function looks like a straw-man to me. I've not used a goto since I stopped writing in FORTRAN in 1978, and not missed it [1]. Neither do I ever have deeply nested if-then-else - these are a good source of bugs. I suppose the rest of your article might have been dealing with simplifying val_nested() but TBH I wasn't interested enough to find out. [1] Not quite true - a Pascal compiler I once had to use in 1983 lacked a return statement, so I had to fake it by putting a 999: label at the end of the function and goto-ing to that. -- Cheers -- Tim
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
