first_block(); //runs first_block and then GOTO to default blank_function if($condition_is_met
first_block(”second_block”); //runs first_block and then GOTO to second_block if($condition_is_met
third_block(”first_block”); //runs first_block and then GOTO to second_block if($condition_is_met)

function first_block($exitfunction=”blank_function”){
if($condition_is_met){$exitfunction();}
}

function second_block($exitfunction=”blank_fucntion”){
if($condition_is_met){$exitfunction();}
}

function third_block($exitfunction=”blank_fucntion”){
if($condition_is_met){$exitfunction();}
}

function blank_function{return true;}

- Leave this room, you’ll see a step, step one floor down. If you were doing something in that room just end it, leave the room, go one floor down. If you were doing something there, end it and go one floor down. In that room you had asked somebody a question, receive the answer even if you don’t need it anymore, now step one down again. You are now on the ground floor. Go straight forward. You will be asked if you want to turn right or left. Turn right, then go straight ahead. Now you are now at the restaurant! Enjoy.

- Thanks. But, eh, out of this window I can see a big sign where it says “Restaurant”. It is there?

- Yes!

- Why didn’t you point and just tell me to go to there?

- No, we use structured language here. “Go to” is unprofessional and can so easily lead to confusion! You have walked to where you are in a structured way. Now you must leave in the same way.

- Really? I wish you could have made an exception in my case.

- Ah, an EXCEPTION! But did you TRY something? If so I will throw an exception, and if you have set up a CATCH, you will save a lot of time.

- So, I should go back an set up a TRY. Is that more structured?

- Far more. That is the pro way of doing it!

- But I am in a hurry. I will simply take the elevator down, and go to the restaurant.

- It’s just so wrong. Nobody can have respect for that. Please Sir, do yourself a favor. Leave this room, you’ll see a step, step one floor down. If you were doing something in that room…


if ($error) {
print "error message";
goto FOOTER;

FOOTER;
include("./graphicdesign/footer.inc");


vs.


if ($error) {
print "error message";
}
else {
# do useful stuff here
}

include("./graphicdesign/footer.inc");


I would really like to see a example with sence…

‘I thoguth it is a joke’
thoguth

‘This is a clear sign of the low quality of the PHP community’
It’s reflects on the “community” poorly?

‘Spaghetti coder now are using classes and objects’
Grammar.

‘How needs a goto statement?’
Who’s how?

‘easyness’
is that like peasyness?

‘permits to everyone’
lol

‘languages has’
grammar

‘estblished’
Taking abbreviations a little too seriously…

‘The goto in PHP is a clear sign of the wrong mantality of the PHP community sites.’
This sounds familiar!

Okay, I’m done >>

My respect for PHP is going down and down. I thoguth it is a joke, but in PHP 5.3 there is goto. This is a clear sign of the low quality of the PHP community, especially compared to Java, Python, Ruby, Groovy etc.

Spaghetti coder now are using classes and objects, but their mentality is still the same. How needs a goto statement? Spaghetti coders. The easyness of PHP permits to everyone to use it and there are some drawbacks from this.

While the other languages has a clear syntax, a well estblished error management, real OOP capabilities, PHP has a different error management for different functions, not overloading/polymorphism…

The goto in PHP is a clear sign of the wrong mantality of the PHP community sites.

This confirms that I will use a different language in the future.

Having said that, there is *one* good reason for adding goto, and that is for compilers that target PHP. For example, a good functional language like Haskell does things like tail-recursion optimization. Now in trivial cases, you can translate tail-recursion into a simple while loop, but in cases where you’re dealing with mutually recursive functions, a while loop doesn’t cut it.

Haskell doesn’t have GOTO statements. Nor does it have for or while loops (you are strictly limited to recursion). Nor can you change a variable once you have assigned it a value.

Nonetheless, you can do wonderful things in Haskell! Indeed, by getting rid of variables, it becomes a lot easier to debug programs, because functions generally don’t have “side effects” that do weird things, like unexpected changing of global variables.

If only it didn’t take so long to get used to the syntax…