ScotlandPHP 2016


Quando il PHP inizia a esaminare un file, cerca i tag di apertura e di chiusura, che sono <?php e ?>, i quali indicano dove iniziare e terminare l'interpretazione del codice. Questa tecnica permette al PHP di essere incorporato in tutte le tipologie di documenti, poiché ogni cosa esterna ai tag di apertura e di chiusura viene ignorata dal parser PHP.

PHP permette anche dei tag aperti abbreviati <? (che sono sconsigliati in quanto sono disponibili solo se abilitati con la direttiva short_open_tag nel file di configurazione php.ini, oppure se PHP è stato configuration con l'opzione --enable-short-tags ).

Se un file contiene solo codice PHP, è consigliato di omettere il tag di chiusura PHP alla fine del file. Questo evita che vengano aggiunti spazi o ritorni a capo dopo il tag di chiusura, che può creare effetti indesiderati poiché PHP comincerà a processare l'output quando in realtà non c'è intenzione da parte dello sviluppatore di inviare dell'output in quella parte dello script.

echo "Hello world";

// ... altro codice

echo "Last statement";

// lo script finisce qui senza tag di chiusura

add a note add a note

User Contributed Notes 5 notes

crazytonyi at gmail dot com
6 months ago
Regarding earlier note by @purkrt :

> I would like to stress out that the opening tag is "<?php[whitespace]", not just "<?php"

This is absolutely correct, but the wording may confuse some developers less familiar with the extent of the term "

Whitespace, in this context, would be any character that generated vertical or horizontal space, including tabs ( \t ), newlines ( \n ), and carriage returns ( \r ), as well as a space character ( \s ). So reusing purkrt's example:

<?php/*blah*/ echo "

would not work, as mentioned, but :

<?php /*php followed by space*/ echo "

will work, as well as :

/*php followed by end-of-line*/ echo "

and :

<?php    /*php followed by tab*/ echo "

I just wanted to clarify this to prevent anyone from misreading purkrt's note to mean that a the opening tag --even when being on its own line--required a space ( \s ) character. The following would work but is not at all necessary or how the earlier comment should be interpreted :

/*php followed by a space and end-of-line*/ echo "

The end-of-line character is whitespace, so it is all that you would need.
purkrt at gmail dot com
1 year ago
I would like to stress out that the opening tag is "<?php[whitespace]", not just "<?php". While this might seem blatantly obvious, I thought for some time that

<?php/*blah*/ echo "

would work, and it does not; the comment does not work as whitespace. I've run into this while converting some older code with short open tag.
jcastromail at yahoo dot es
7 months ago
Its important:

this code (for web)
    <? echo "am;" ?>

Generates the next result:
instead of
The last tag "?>" deletes the end of the line.

However, if we changed the line
    <? echo "am"; ?>
    <? echo "am"; ?>.  (or  a space)
then the result is :
1 year ago
A few related notes, partly covered elsewhere in the manual:

  → Since PHP 5.4 the inline echo <?= ?> short tags are always
    enabled regardless of the short_open_tag (php.ini) setting.

  → PHP tags are infrequently also referred to as open/close "tokens"
    (as per the tokenizers T_OPEN_TAG / _ECHO, and T_CLOSE_TAG naming).

  → The historic ASP-style <% %> and even more rarely used
    <script language=PHP></script> tags are to be repealed in PHP7.

There also exists a small tool called "phptags tidier" for consistently rewriting PHP short/long tags.  It's suitable to normalize include and template scripts, e.g. employ the always-enabled long <?php ?> tags, and/or relieve whitespace padding before/after PHP tags:

    phptags --long --whitespace --warn  *.php

Instead of reliably fixing the common whitespace/BOM issues around tags, it can also just remove all ?> close tags with `--unclose --tokenizer` as advised afore.
alexander dot podgorny at somewhere dot com
1 year ago
One reason to use long tags over short is to avoid confusion with <?xml ?> notation.
To Top