TYPO3 Core

I can explain why those two expressions give different results. The "problem" here in a nutshell is that two different expressions and two different treatments get applied to the value:

• In tag mode, the value is always considered a string and is trimmed for quotes, then checked if it is numeric and if so, a NumericNode is created (without casting the value). NumericNode internally does not explicitly cast, but rather adds zero to the value. This preserves the initial type and if the passed value is a string containing a zero, adding a zero to it creates an integer.
• In inline mode, the value is part of an array expression and a different detection routine is used to detect hardcoded numbers (and only those; e.g. not numbers coming from a variable!). This matches your case and the result of such a match is actually cast to (float) by the TemplateParser (the input is also a string). But contrary to tag mode, using a number in an array does not create a NumericNode and the add-zero pseudo-casting does not happen.

Phew. I hope that's understandable without knowing the internals.

This explains why you end up with two different data types in your particular case, and it is by design in both cases but two different solutions were chosen (the float cast is very old - the add-zero in NumericNode is fairly new). And you can certainly make the argument that this should be uniform - which I would say should be done by doing the same add-zero trick in TemplateParser instead of as it is now, casting the value to a float (which then becomes a double internally in PHP).

Variable assignent in compiled templates reported on https://github.com/TYPO3/Fluid/issues/334