TYPO3.Flow

btw: this reduces the execution time within ObjectAccess from > 40% to below 10% in the given example

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/16234

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/16234

Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/16234

Patch set 5 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/16234

Patch set 6 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/16234

Patch set 7 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/16234

I didn't manage to test this while it was hot, but now I realized that this breaks the Form framework (and probably some more).
In my case FormRuntime::getCurrentPage() always returns NULL – because FormRuntime implements \ArrayAccess but $formRuntime['currentPage'] returns FALSE.

To reproduce create a class extending \ArrayAccess and providing some additional custom getter. This getter can't be called via ObjectAccess

A simple test case to reproduce this:

$arrayObject = new \ArrayObject();
var_dump($arrayObject->getIteratorClass());
var_dump(\TYPO3\Flow\Reflection\ObjectAccess::getProperty($arrayObject, 'iteratorClass'));

Should output "ArrayIterator" twice, but the second time an exception #1263391473: The property "iteratorClass" on the subject was not accessible is thrown.
Commenting out 113 & 114 in ObjectAccess fixes this issue for me.

I'll write tests and push a follow up

Patch set 1 for branch composer has been pushed to the review server.
It is available at https://review.typo3.org/19347