[TYPO3-50-general] OrthoScript

[Martin Ficzel]

Elmar Hinz schrieb:
> Hi team,
> 
> you probably share the experience, that many new developers are irritated
> by the PHP representation of Typoscript with dots at the end of the
> key names. I suggest an inversion of this for TYPO3 5.0 by the following
> model:

the problem of ts-parsing is that it is essential that a key can have a
value and subkeys wich is not possible with multi diensional arrays.

so why do we use php arrays if they do'nt fit our needs?

i suggest to examine alternative datastructures before deciding how ts-2
should be parsed at all.

the advantage of php arrays is an efficient implementation in php. but
php does also suport native-xml handling and xml can store attributes
and children.

why not think about parsing ts to an internal xml-structure. i also
think that it's makes no sense to use xml as a writing format (in the
post above i just wanted to point out some similarities) and i do'nt
think that the xml-structure should be serialized to a string at all. so
 imho the verbosity of xml does not really count in case of internal using.

another alternative would be the use of the composite pattern but i fear
that would cause major performance problems.

regards Martin

PS: i just want to give input to the discussion. i know there are 1000
reasons to keep using arrays but we have to discuss the alternatives.