[TASK] Small cleanup in detection of form ViewHelper scope
[FEATURE] Format / RegularExpression ViewHelper
Merge pull request #320 from NamelessCoder/regularexpression

[FEATURE] Format / RegularExpression ViewHelper
[BUGFIX] Enable setting of tagName in LanguageMenuViewHelper
[TASK] Improve test suite
Merge pull request #321 from NamelessCoder/tests

[TASK] Improve tests
Merge pull request #322 from DATAWERK/fixes_LanguageMenuViewHelper

[BUGFIX] Enable setting of tagName in LanguageMenuViewHelper
[FEATURE] Add isLanguage ViewHelper
Merge pull request #329 from bjo3rnf/islanguage

[FEATURE] Add isLanguage ViewHelper
[TASK] TypoLink ViewHelpers

Those ViewHelpers render typoLink compatible parameter arrays to URIs/Anchors
Merge pull request #331 from cedricziel/typolinkViewHelper

[FEATURE] TypoLink ViewHelpers
[FEATURE] Chunk ViewHelper

array_chunk() is a really helpful function which functionality should be available as a ViewHelper.

Fx if you have an Array of pages from v:page.menu and want to allocate these links to a fixed number of container elements this would be much code without this ViewHelper.

Fx we have 9 links which shall be placed in 2 containers of same count of items each, if odd the first container takes more all.

Expected html markup:
<div class="container1">
<a>1. Link</a>
<a>2. Link</a>
<a>3. Link</a>
<a>4. Link</a>
<a>5. Link</a>
</div>
<div class="container2">
<a>6. Link</a>
<a>7. Link</a>
<a>8. Link</a>
<a>9. Link</a>
</div>

With this ViewHelper this is an easy task:
{links->v:iterator.chunk(count:2,fixed:1)->v:var.set(name:'chunks')}
<div class="container1">
<f:for each="{chunks.0}" as="item">{item}</f:for>
</div>
<div class="container2">
<f:for each="{chunks.1}" as="item">{item}</f:for>
</div>
[BUGFIX] Use ctype_digit instead of is_numeric

The is_numeric function returns TRUE on fx string "z123" which ctype_digit does not - it's preferable to return FALSE on strings like this.
[BUGFIX] Use PREG_SET_ORDER on preg_match_all

This causes the $matches array to be filled in a way which allows the subsequent conditions to function properly when $global = TRUE.
[BUGFIX] Abstract Iterator returns FALSE if item is in position zero

Casting to boolean replaced with check for strict FALSE !==.
[BUGFIX] Single Math ViewHelpers used incorrect value when $a is Iterator
[BUGFIX] Multiple Math ViewHelpers used incorrect value when $a is Iterator
[BUGFIX] Multiple Math ViewHelpers performed Iterator access check on non-Iterators
[BUGFIX] Math / Median uses incorrect slicing point and midpoint calculation
[BUGFIX] Ensure consistent return type in Math / Range ViewHelper