(PHP 4, PHP 5, PHP 7)

printВыводит строку


int print ( string $arg )

Выводит arg.

print не является "настоящей" функцией (это конструкция языка), поэтому заключать аргументы в скобки необязательно.

Список параметров


Вводимые данные.

Возвращаемые значения

Возвращает 1, всегда.


Пример #1 Примеры использования print

print("Привет мир!");

"print() можно использовать и без скобок.";

"Это займет
несколько строк. Переводы строки тоже

"Это займет\nнесколько строк. Переводы строки тоже\nвыводятся";

"Экранирование символов делается \"Так\".";

// с print можно использовать переменные ...
$foo "foobar";
$bar "barbaz";

"foo - это $foo"// foo - это foobar

// ... и массивы
$bar = array("value" => "foo");

"это {$bar['value']} !"// это foo !

// При использовании одиночных кавычек выводится имя переменной, а не значение
print 'foo - это $foo'// foo - это $foo

// Если вы не используете другие символы, можно вывести просто значения переменных
print $foo;          // foobar

print <<<END
Здесь используется синтаксис "here document" для вывода
нескольких строк с подстановкой переменных 
Заметьте, что закрывающий идентификатор должен
располагаться в отдельной строке, никаких пробелов!


Замечание: Поскольку это языковая конструкция, а не функция, она не может вызываться при помощи переменных функций.

Смотрите также

  • echo - Выводит одну или более строк
  • printf() - Выводит отформатированную строку
  • flush() - Сброс системного буфера вывода
  • Heredoc синтаксис


This is a simple function for printing debug comments that I didn't think of for a long time. Maybe it'll serve you good too.


function printd($str) {
  if (
$debug) { echo $str; }

// ...

if ($valueCalculatedEarlierInTheScript == 3) {
printd("doSomethingWithNoOutput() has executed.");


It's mostly just to make sure everything is running without having to go through everything and put in echo "Step #whatever has executed" whenever something mysterious isn't working.
2005-07-16 18:10:07
I have a small utility run from the command line that processes a potentially huge list of files. As it can take hours to complete, I stuck a 

print '.';

statement in the body of the main loop to prove that something was  happening.

For reasons unknown to me, the utiliity suddenly started buffering the output such that it printed nothing until completion, defeating the purpose of the running monitor. Adding flush() statements did nothing. The problem was solved by using

fputs(STDOUT, '.');

but I have no idea why.
2005-12-05 15:48:38
I have written a script to benchmark the several methods of outputting data in PHP: via single quotes, double quotes, heredoc, and printf. The script constructs a paragraph of text with each method. It performs this construction 10,000 times, then records how long it took. In total, it prints 160,000 times and records 16 timings. Here are the raw results.

Outputted straight to browser--

Single quotes: 2,813 ms
...with concatenation: 1,179 ms
Double quotes: 5,180 ms
...with concatenation: 3,937 ms
heredoc: 7,300 ms
...with concatenation: 6,288 ms
printf: 9,527 ms
...with concatenation: 8,564 ms

Outputted to the output buffer--

Single quotes: 8 ms
...with concatenation: 38 ms
Double quotes: 8 ms
...with concatenation: 47 ms
heredoc: 17 ms
...with concatenation: 49 ms
printf: 54 ms
...with concatenation: 52 ms

A nice graph of the script's output can be found here:

So what should you choose to print your text? I found several things out writing this.

First, it should be noted that the print and echo keywords are interchangeable, performance-wise. The timings show that one is probably an alias for the other. So use whichever you feel most comfortable with.

Second, if you've ever wondered which was better, the definitive answer is single quotes. Single quotes are at least four times faster in any situation. Double quotes, while more convenient, do pose a debatably significant performance issue when outputting massive amounts of data.

Third, stay away from heredoc, and absolutely stay away from [s]printf. They're slow, and the alternatives are there.

The source of my script can be found here:

DO NOT RUN THE SCRIPT ON THE INTERNET! Run it instead from localhost. The script outputs ~45 megabytes of text in an html comment at the top of the page by default. Expect the benchmark to take ~45 seconds. If this is too long, you can change the amount of iterations to a lower number (the results scale accurately down to about 1,000 iterations).
2006-05-20 22:41:08
the FAQTs article can be found archived at

(url split to get past the line-length limitation)
2007-06-01 10:19:48
I wrote a println function that determines whether a \n or a <br /> should be appended to the line depending on whether it's being executed in a shell or a browser window.  People have probably thought of this before but I thought I'd post it anyway - it may help a couple of people.

function println ($string_message) {
$_SERVER['SERVER_PROTOCOL'] ? print "$string_message<br />" : print "$string_message\n";


Running in a browser:

<?php println ("Hello, world!"); ?>
Output: Hello, world!<br />

Running in a shell:

<?php println ("Hello, world!"); ?>
Output: Hello, world!\n
2008-05-16 07:08:09
Be careful when using print. Since print is a language construct and not a function, the parentheses around the argument is not required.
In fact, using parentheses can cause confusion with the syntax of a function and SHOULD be omited.

Most would expect the following behavior:
if (print("foo") && print("bar")) {
// "foo" and "bar" had been printed

But since the parenthesis around the argument are not required, they are interpretet as part of the argument.
This means that the argument of the first print is

    ("foo") && print("bar")

and the argument of the second print is just


For the expected behavior of the first example, you need to write: 
if ((print "foo") && (print "bar")) {
// "foo" and "bar" had been printed
2008-08-25 12:45:55
An update to the println function I wrote below, this is a more efficient, correct and returns a value (1, always; (print)).


function println($string_message '') {
        return isset(
$_SERVER['SERVER_PROTOCOL']) ? print "$string_message<br />" PHP_EOL:
$string_message PHP_EOL;

2008-08-28 10:46:20
mvpetrovich of 2007 could just use single quotes as his string delimiters (see the example in the current documentation).
It's not ALWAYS appropriate, but generally it is best (the Zend Framework coding standards have a good take on this). It yields a number of interesting benefits:
1: Nobody will be tempted to write functions to replace backticks or other characters with double quotes. Such functions may cause a (negligible) loss of efficiency, and maybe other undesired effects.
2: You will be able to use double quotes without escaping. This is recommended (although not required) for HTML and XML attributes, as well as quoted text.
3: The script will hit the browser very slightly slightly faster since PHP doesn't have to scan through the string looking for variables, escaped characters, curly braces or other things.
4: Your code gets ten times easier to read. (as mvpetrovich pointed out)

If, in spite of these four excellent benefits, you really MUST still use double quotes to delimit boring old string constants (and seriously, why would you?), you could use the slightly less favourable single quotes as delimiters for most markup languages.
HTML served as HTML will even let you lay out unquoted attributes (yuck).

It should also be noted though that if you are just printing bare strings, you may as well shut off the php parser. The quickest way to send a string is to write it as plain text, OUTSIDE of the php tags. This will also make your code look excellent in a lot of syntax highlighters.

There are few disadvantages to doing this, if any. Output buffering still works. All your classes and objects and includes remain in place. Your script runs faster. World peace is obtained.
2009-10-01 04:20:28
Don't rely on parenthesis used for `print` construct:

print 1 . print(2) + 3;
print PHP_EOL;
print 1 . (print(2)) + 3;
2018-01-27 15:42:10

    Поддержать сайт на родительском проекте КГБ