Variable functions call a function whose name is stored in a variable.
What It Does
Variable functions call a function whose name is stored in a variable. The following examples distinguish a normal use case, a boundary case and a practical application.
Requirements and Compatibility
PHP 8.x and a local test environment. Apply input validation, correct error handling and the requirements of any optional libraries.
The code focuses on the core concept. Production implementation may also need routes, validation, persistence, authorization or deployment tooling.
Example 1: Basic Behavior
Start with the smallest meaningful working case.
<?php
function upperWord(string $word): string { return strtoupper($word); }
$callable = 'upperWord';
echo $callable('php');
Example 2: Another Case
Examine the edge case and the observable result.
<?php
$actions = ['trim' => 'trim', 'lower' => 'strtolower'];
echo $actions['lower']('HELLO');
Practical Example: Putting It to Use
Apply the technique to a small practical task.
<?php
$allowed = ['strlen', 'strtoupper'];
$name = 'strlen';
if (!in_array($name, $allowed, true)) throw new RuntimeException('Not allowed');
echo $name('example');
Important Behavior and Edge Cases
Never call arbitrary user-supplied names; maintain an allowlist of intended callables.
Comparison with Related Functions or Approaches
| Option | What it means in practice |
|---|---|
| Variable Functions and Dynamic Calls | Variable functions call a function whose name is stored in a variable. |
| Related approach | Closures or a dispatch table provide safer explicit behavior. |
Common Beginner Mistakes
| Mistake | Correct approach |
|---|---|
| Ignoring the important boundary for Variable Functions and Dynamic Calls | Never call arbitrary user-supplied names; maintain an allowlist of intended callables. |
| Assuming a related mechanism has the same behavior | Closures or a dispatch table provide safer explicit behavior. |
Key Takeaways
- Variable functions call a function whose name is stored in a variable.
- Never call arbitrary user-supplied names; maintain an allowlist of intended callables.
- Closures or a dispatch table provide safer explicit behavior.
Before adapting these examples, verify the return values, test the failure paths and confirm that your application meets its security and environment requirements.