What is the difference between a language construct and a built-in function in PHP?

What is the difference between a language construct and a built-in function in PHP?

(This is longer than I intended; please bear with me.)

Most languages are made up of something called a syntax: the language is comprised of several well-defined keywords, and the complete range of expressions that you can construct in that language is built up from that syntax.

For example, lets say you have a simple four-function arithmetic language that only takes single-digit integers as input and completely ignores order of operations (I told you it was a simple language). That language could be defined by the syntax:

// The | means or and the := represents definition
$expression := $number | $expression $operator $expression
$number := 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
$operator := + | - | * | /

From these three rules, you can build any number of single-digit-input arithmetic expressions. You can then write a parser for this syntax that breaks down any valid input into its component types ($expression, $number, or $operator) and deals with the result. For example, the expression 3 + 4 * 5 can be broken down as follows:

// Parentheses used for ease of explanation; they have no true syntactical meaning
$expression = 3 + 4 * 5
            = $expression $operator (4 * 5) // Expand into $exp $op $exp
            = $number $operator $expression // Rewrite: $exp -> $num
            = $number $operator $expression $operator $expression // Expand again
            = $number $operator $number $operator $number // Rewrite again

Now we have a fully parsed syntax, in our defined language, for the original expression. Once we have this, we can go through and write a parser to find the results of all the combinations of $number $operator $number, and spit out a result when we only have one $number left.

Take note that there are no $expression constructs left in the final parsed version of our original expression. Thats because $expression can always be reduced to a combination of other things in our language.

PHP is much the same: language constructs are recognized as the equivalent of our $number or $operator. They cannot be reduced into other language constructs; instead, theyre the base units from which the language is built up. The key difference between functions and language constructs is this: the parser deals directly with language constructs. It simplifies functions into language constructs.

The reason that language constructs may or may not require parentheses and the reason some have return values while others dont depends entirely on the specific technical details of the PHP parser implementation. Im not that well-versed in how the parser works, so I cant address these questions specifically, but imagine for a second a language that starts with this:

$expression := ($expression) | ...

Effectively, this language is free to take any expressions it finds and get rid of the surrounding parentheses. PHP (and here Im employing pure guesswork) may employ something similar for its language constructs: print(Hello) might get reduced down to print Hello before its parsed, or vice-versa (language definitions can add parentheses as well as get rid of them).

This is the root of why you cant redefine language constructs like echo or print: theyre effectively hardcoded into the parser, whereas functions are mapped to a set of language constructs and the parser allows you to change that mapping at compile- or runtime to substitute your own set of language constructs or expressions.

At the end of the day, the internal difference between constructs and expressions is this: language constructs are understood and dealt with by the parser. Built-in functions, while provided by the language, are mapped and simplified to a set of language constructs before parsing.

More info:

  • Backus-Naur form, the syntax used to define formal languages (yacc uses this form)

Edit: Reading through some of the other answers, people make good points. Among them:

  • A language builtin is faster to call than a function. This is true, if only marginally, because the PHP interpreter doesnt need to map that function to its language-builtin equivalents before parsing. On a modern machine, though, the difference is fairly negligible.
  • A language builtin bypasses error-checking. This may or may not be true, depending on the PHP internal implementation for each builtin. It is certainly true that more often than not, functions will have more advanced error-checking and other functionality that builtins dont.
  • Language constructs cant be used as function callbacks. This is true, because a construct is not a function. Theyre separate entities. When you code a builtin, youre not coding a function that takes arguments – the syntax of the builtin is handled directly by the parser, and is recognized as a builtin, rather than a function. (This may be easier to understand if you consider languages with first-class functions: effectively, you can pass functions around as objects. You cant do that with builtins.)

Language constructs are provided by the language itself (like instructions like if, while, …) ; hence their name.

One consequence of that is they are faster to be invoked than pre-defined or user-defined functions (or so Ive heard/read several times)

I have no idea how its done, but one thing they can do (because of being integrated directly into the langage) is bypass some kind of error handling mechanism. For instance, isset() can be used with non-existing variables without causing any notice, warning or error.

function test($param) {}
if (test($a)) {
    // Notice: Undefined variable: a

if (isset($b)) {
    // No notice

*Note its not the case for the constructs of all languages.

Another difference between functions and language constructs is that some of those can be called without parenthesis, like a keyword.

For instance :

echo test; // language construct => OK

function my_function($param) {}
my_function test; // function => Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING

Here too, its not the case for all language constructs.

I suppose there is absolutely no way to disable a language construct because it is part of the language itself. On the other hand, lots of built-in PHP functions are not really built-in because they are provided by extensions such that they are always active (but not all of them)

Another difference is that language constructs cant be used as function pointers (I mean, callbacks, for instance) :

$a = array(10, 20);

function test($param) {echo $param . <br />;}
array_map(test, $a);  // OK (function)

array_map(echo, $a);  // Warning: array_map() expects parameter 1 to be a valid callback, function echo not found or invalid function name

I dont have any other idea coming to my mind right now… and I dont know much about the internals of PHP… So thatll be it right now ^^

If you dont get much answers here, maybe you could ask this to the mailing-list internals (see http://www.php.net/mailing-lists.php ), where there are many PHP core-developers ; they are the ones who would probably know about that stuff ^^

(And Im really interested by the other answers, btw ^^ )

As a reference : list of keywords and language constructs in PHP

What is the difference between a language construct and a built-in function in PHP?

After wading through the code, Ive found that php parses some of statements in a yacc file. So they are special cases.

(see Zend/zend_language_parser.y)

Apart from that I dont think that there are other differences.

Leave a Reply

Your email address will not be published.