Cover image for post GOSUB for PHP

GOSUB for PHP

Attention: This post is an April fool hoax! There are no plans by anybody for GOSUB or similar in PHP!

Since version 5.3 the PHP programming language finally supports the GOTO operator. GOTO is a standard construct in high-level programming languages and has a long history in paradigm of structured programming. The GOTO statement allows to solve daily programming tasks, like implementing finite state machines, very easily and comfortably. GOTO constructs raise the code quality of such implementations drastically.

PHP supports so-called labeled GOTO, in lack of forced source code line numbering. An example of how GOTO works in PHP is shown below:

<?php $counter = 0; main: $counter++; echo "I'm in main\n"; if ( $counter <= 5 ) { goto subroutine; } else { exit; } subroutine: echo "I'm in sub routine\n"; goto main; ?>

main and subroutine are labels in this simple PHP script. Inside the if statement, the script performs a jump to the label subroutine, if the $counter is not larger than 5, yet. This jump results in the execution flow to jump to line 20, where the label is declared. After printing out the text, another jump is performed, back to the main label.

As can be seen in this example, a major drawback in the PHP implementation of GOTO is that the more advanced version GOSUB is not supported, yet. The GOSUB statement allows you to return from a sub-routine right to the next statement after the jump. It allows you to simplify the code above drastically as can be seen below:

<?php $counter = 0; while ( $counter < 5 ) { echo "I'm in main\n"; $counter++; gosub subroutine; } subroutine: echo "I'm in sub routine\n"; return; ?>

In this script, GOSUB is used instead of GOTO, making the main label unnecessary. The return statement after the subroutine label makes the execution flow jump right back to the next statement after the GOSUB call. Beside cleaning up the shown code, GOSUB has the drastic benefit, that it makes labeled sub-routines re-usable: The jump back is not bound to a fixed label, but returns to the place where the routine was entered.

To fix this drastic drawback against more advanced GOTO implementations, like e.g. in Basic, the PHP core developers decided to delay the release of PHP 5.3 once more. The current release candidate state of PHP 5.3 is canceled and the development team is now working on another alpha version. Due to the complex changes necessary in the parser, the stable version of PHP 5.3 can not be expected before January 2010.

Rasmus Lerdorf, the inventor of PHP, stated, that he is highly pleased to see this change coming in so straightforward. He is sure, that this is an important addition to the PHP programming language and supports the newly decided delay of version 5.3 to fix the misery. Rasmus said: "It is unacceptable that PHP is struck off by other high-level languages like Basic".

Comments

you are absolutely right! It's a shame to not have a complete goto/gosub implementation!

;)

fullo at 2009-04-01

I'm currently using the object-oriented possibilities of PHP, but that's only because the better things like "goto" and "gosub" aren't currently availiable. It would be a very nice addition to the language indeed.

;)

berry at 2009-04-01

Why would you need gosub when there are functions?

Wolfgang Stengel at 2009-04-01

This must be some sort of April fools day joke, surely?

Please, let it be. It was a -beep- mistake having GOTO in PHP but now GOSUB?

May I suggest to the individual(s) responsible that they GOTO -beep- ? ;)

I'm not really amused and if this is the route that PHP is taking, then it's a very bleak, black day for PHP developers the world over.

Les at 2009-04-01

I would be great if one day all my C64 Basic programs would run in PHP!

mor10am at 2009-04-01

I totally agree with Les. It's the exact opposite to all I have learned at the University. If you only mentioned the word GOTO you just about failed the course instantly....

Patrick at 2009-04-01

@mor10am: Full ACK!! I hereby propose implementing PEEK and POKE next. After that is done, we can replace require and include with LOAD "*",8,1 :-P

Markus at 2009-04-01

It requires your server to have the 16k RAM pack

Engelbert at 2009-10-01

@Engelbert: LOL ;)

Toby at 2009-10-02