'We\'ve' . "all $een" . 'this' . $problem . 'before' . $and->it . ((1==1) ? 'seems' : 'dosen\'t seem') . sprintf('about time to %s things', 'clarify');
PHP string handling can be a tough concept to wrangle. Developers have many options: single / double quotes, concatenation and various string manipulation functions. The choices you make have a significant impact on the readability and performance of your script. Let's meet the line-up:
Single quotes are used to define a string whose contents should be taken literally. What this means is that PHP will not attempt to expand any content contained between the
This is the way to tell your favorite Hypertext Preprocessor, "That little guy? Don't worry about that little guy."
In most cases this is the de-facto standard for strings. However, when a decent number of variables become involved it tends to become difficult to keep your quotes accounted for. When combining simple strings with variables and single quotes, the "
." operator is needed between each variable/string. That "
." is known as the concatenation operator.
$date = 'Yesterday';
$location = 'outside';
$item = array ( 'description' => 'lovely', 'name' => 'butterfly');
$content = $date . ' I went ' . $location . ' and caught a ' . $item['description'] . ' ' . $item['name'];
Output: Yesterday I went outside and caught a lovely butterfly
Using double quotes will cause PHP to look a little closer into the string to find anywhere it can "read between the lines." Variables and escape characters will be expanded, so you can reference them inline without the need for concatenation. This can be useful when creating strings which include pre-defined variables.
$file = 'example.jpg'
$content = "<a href=\"http://www.example.com/$file\">$file</a>"
Output: <a href="http://www.example.com/example.jpg">example.jpg</a>
In previous versions of PHP there was a significant performance difference between the use of single v. double quotes. In later versions performance variations are negligible. The decision of one over the other should focus on feature and readability concerns.
Unlike single and double quotes, the
sprintf function comes to the table with a few cards up its sleeve. When provided with a formatting "template" and arguments,
sprintf will return a formatted string.
$order = array ( 'item' => 'RC Helicopters', 'status' => 'pending');
$content = sprintf('Your order of %s is currently %s', $order['item'], $order['status']);
Output: Your order of RC Helicopters is currently pending
When constructing a complex string such as XML documents,
sprintf allows the developer to view the string with placeholders rather than a mish-mash of escaped quotes and variables. In addition
sprintf is able to specify the type of variable, change padding/text alignment, and even change the order in which it displays the variables.
The debate over the most efficient method of string definition has raged for years and will likely continue ad infinitum. However, when the benchmarks show their performance as almost identical, it leaves you with one major question: What works the best for your implementation? Typically my scripts will contain all of the methods above, and often a combination of them.
print(sprintf('The %s important thing is that %s give them all a try and see for %s', 'most', 'you', 'yourself'));