[TYPO3-core] RFC: Extend TypoScript values

[Michael Stucki]

Hi Martin,

> I'm missing "replaceString". I know we could gon on and add an endless
> list of functions, but I hace written PHP-functions to overcome this
> stdWrap limitation.

You can for now write a hook for this because there is probably not enough
time anymore to fix this.

> Problem is the syntax (also a problem for addString)
> 
> Easy.
> 
> replaceString(old,new)
> 
> But what about these?
> 
> replaceString(o\,ld,ne\)w)
> replaceString("o,ld","ne)w")
> replaceString("o'ld","new")
> replaceString('o"ld','ne)w')
> replaceString("o\"ld","new")
> 
> Which one shall be valid?

I suggest to use pipe symbols like it is used in several other places in TS.
The reason is that I think the comma is more often used in strings, then it
could cause a conflict (like in your example above).

Just another idea: You could write an "eval" function that assigns the
current value of <object path> to $input and expects to write it to
$output...

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/