When Rasmus Lerdorf first put PHP together, he – quite sensibly, despite his heritage – chose not to write it in Greenlandic or Danish. Good job too – that would have been rather unpleasant to work with. He opted instead, being in Canada at the time, for the local tongue. No, not French – that bastard dialect of the Queen’s English commonly referred to as “US English”.

PHP developers in Britain have been grumpy about this ever since. What was he thinking? And more importantly, how do we undo this travesty? How do we developers ensure the traditions of the British Empire continue to be upheld, even in the digital age?



A Slap in the Face

$variable_name

The first, but maybe the most important, of many changes that will allow PHP to achieve a more elegant feel is to remove that symbol so beloved by the US and replace it with something altogether more refined. More solid. More … sterling.

£variable_name

Abbreviations

Few things are more abhorrent to the British than unnecessary abbreviations. “Text speak” is unheard of on the streets of London, as the natural ingrained British grammarian simply refuses to stoop to sending messages of the “c u soon traffic kthxbye” variety, instead proferring something altogether more elegant: “Dear Sir/Madam. I will arrive as soon as time allows, which I expect to be within the hour. I assure you the horses shall not be spared. Yours respectfully.” (slower to type, yes, but we do not like to be rushed).

PHP, on the other hand, is full to bursting with abbreviations and acronyms which are entirely unnecessary:

str_replace ( ) is_int ( ) var_dump ( ) preg_match ( ) json_encode ( ) mysql_connect ( )

The following changes should improve things:

string_replace ( ) is_integer ( ) variable_dump ( ) perform_a_regular_expression_match ( ) javascript_object_notation_encode ( ) my_structured_query_language_connect ( )

Eloquence

if ( $condition ) { // Code here } else { // Code here }

Shakespeare would be ashamed to see his native tongue twisted into this monstrosity. Brevity is to be applauded in the right context – in some dark corner, where it shall be seldom seen – but not here. The if … else block is the most used conditional code in all of PHP, so it must be made as inoffensive as possible. There are many options for its replacement, but this may be the strongest:

perchance ( £condition ) { // Code here } otherwise { // Code here }

Spelling

imagecolorallocate ( ) serialize ( ) newt_centered_window ( ) connection_status ( )

Words fail me at this point. How is any self-respecting gentleman expected to make head or tail of these “words”. It beggars belief that anyone could allow such distortions of words to be entered into a programming language. They, along with the myriad of similar errors, should be reverted to their proper forms immediately:

imagecolourallocate ( ) serialise ( ) newt_centred_window ( ) connexion_status ( )

Manners

try { // Code here } catch ( Exception $e ) { // Handle exception die ( 'Message' ) ; }

The try … catch block is an excellent example of PHP’s lack of manners. Far too direct to be allowed in the new PHP. Additionally, the word “die” is so very depressing. This new block, although more verbose, is vastly more polite and upbeat:

would_you_mind { // Code here } actually_i_do_mind ( Exception £e ) { // Politely move on cheerio ( 'Message' ) ; }

Class

Perhaps nothing is as important and ingrained in the British psyche as the notion of class and, while there are few opportunities for change within this part of PHP, the changes that there are to be made here are important.

class Republic { public $a ; private $b ; protected $c ; } $example = new Republic ;

To begin with, the current system has no place for class hierarchy and this is unacceptable. So we shall begin by giving classes specific levels – upper, middle, working – and no class can access the methods of one of a higher level without the explicit permission of the higher order class (of course, though it might then have access, it would not be a true member of the higher order and could not itself grant higher order access to other lower order classes). “Public” and “Private”, in the British class system, are often synonymous (see, for example, school system nomenclature), so these must be adjusted, as should the “Protected” property visibility. The word “new”, while passable, has a much more appropriate replacement in matters of class.

upper_class Empire { state £a ; private £b ; hereditary £c ; } £example = nouveau Empire ;

The Sun Never Sets …

It is hoped that these few simple changes will improve the reputation and status of PHP among other languages. No longer will it be the poor American cousin – instead it can take its rightful place as the – British – King of the scripting languages.

Original Article: http://www.addedbytes.com/blog/if-php-were-british/.