Hi,
We have a specific script to detect files causing troubles with a bad
end or begin file.
The solution of not writing ?> is a solution for the end of the file,
but do not resolve the same problem in beginning of the file.
Regards
Julien
Le 20/05/2011 14:35, Gonéri Le Bouder a écrit :
Hi,
If a trailing white space remains after a PHP closing tag, it will be
sent to the brower
and this can break the data flow sent to the client. For example, if
we want to change the
HTTP header or sent gzipped content. Such issue are very painful to debug.
Another point is for PHP itself a EOF is more simple to parse than a
to the caracter string
"?>".
Is it possible to update the
https://forge.indepnet.net/projects/glpi/wiki/CodingStandards
to forbid such closing tag ?> at the end of the files.
Two related articles:
http://codeigniter.com/user_guide/general/styleguide.html#php_closing_tag
http://blog.rogeriopvl.com/archives/php-files-closing-the-php-tag-or-not/
Best regards,
_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org
https://mail.gna.org/listinfo/glpi-dev
