[TYPO3-v4] Mr. Jenkins will complain about CGL issues
Steffen Gebert
steffen.gebert at typo3.org
Wed Apr 20 10:26:14 CEST 2011
>> Category CharacterAfterPHPClosingTag: "No newline character is allowed
>> ...
> I thought with empty lines also newlines (\n) are mean. Is this not correct?
I would say that exactly one \n is allowed directly after the closing
tag. That's what several IDEs add. However, any other chars after that
should create an output.
I just digged into the funny history of PHP while looking up a reference
for this assertion. See [1]:
> So, to get around the "Headers already sent" errors, Zeev decided to make the PHP ending tag be "?> with an optional newline". It was a heated debate on the PHP Internals (then php-dev) list. So much that I remembered it and dug it up on MARC.
>> Type DisallowElseIfConstruct: is not relevant for us
>
> Have a look at page 12: "TYPO3 code must not use the else if construct."
"else if" is not allowed, "elseif" is - I assume.
Kind regards
Steffen
--
[1] http://brian.moonspot.net/php-history-newline-closing-tag
Steffen Gebert
TYPO3 v4 Core Team Member
TYPO3 .... inspiring people to share!
Get involved: http://typo3.org
More information about the TYPO3-project-v4
mailing list