PHP will never fully be utilized as an OO language by the vast majority of its user base due to its syntactically terrible standard library and history as a functional language.
As such, this addition makes plenty of sense.
I can assure you that PHP is not a functional language (despite all my efforts to make it one).
2) php is procedural, not functional. (edit: whoops, beaten to this punch)
Web pages are just not suited to OO. Encapsulation can be done via functions - adding OO to it gets you nothing except longer code.
Making things more complicated does not make them better.
Maybe some other framework does this better, though.
Welcome to 1980.
10 PRINT "WELCOME TO 1980"
20 GOTO 10While loops limit the scope of variables inside the loop. For C++, that means a variable declared inside cannot be used outside - logical, and OOP.
But PHP has no concept of privacy or scope, even its "rules" may be broken (though not guaranteed to always work) and come out with the right results. Anything will compile, and usually the results are as expected.
So if you have a while loop with no concept of scope or local variables, I guess the restrictions are gone. A number of nested loops with breaks; and continues; all over end so long as the concept of limited data scope/access is not present as in PHP are exactly equivalent to goto as it is.
I guess a language as, shall we say, 'relaxed' as PHP is well-matched with relaxed keywords like goto.
Although, PHP's gotos don't allow they, and PHP still only admits structured control flow.