Add setupFunctions() method to Mocker.

[bayleedev]

This allows you to declare which methods you are going to define later on. This, for instance, may be helpful if something like apc is caching the full namespace of a method. The first time you call a global function, it might be cached, so stubbing it would not work.

[bayleedev]

Looks like it failed hitting google.com in two of the sets in the matrix. These are integration tests, but I still feel we should be stubbing external requests. Imo death to _hasNetwork().

[nateabele]

Sounds like a good opportunity to eat your own setupFunctions() dog food. ;-)

[jails]

Yeah Google seems to fail answering pretty often...

[jails]

Ok after some experiments looks like there's no other way to make things works w/o a executing a setup at a bootstrap level.

Maybe we can complete this PR with a kind of :

if (!Environment::is('production')) {
    Mocker::setupFunctions(array(
        'lithium\util\getmxrr',
        'lithium\console\command\shell_exec',
        'lithium\console\command\is_dir',
        'lithium\net\socket\feof',
        'lithium\net\socket\fopen',
        'lithium\net\socket\stream_socket_client',
        'lithium\net\socket\stream_get_contents',
        'lithium\net\socket\stream_context_create',
        'lithium\net\socket\stream_get_meta_data',
        'lithium\tests\cases\net\socket\stream_context_get_options',
        'lithium\net\socket\curl_init',
        'lithium\net\socket\curl_setopt',
        'lithium\net\socket\curl_close',
        'lithium\net\socket\curl_exec'
    );
}

in a config/boostrap.php in the lithium repo.

I know Environment is not accessible at this stage, but I hope we can refactor the framework on day to set the environnment earlier.

Did you find other solutions ?

[jails]

Vote up on the bug guys: https://bugs.php.net/bug.php?id=63201, with any luck it'll be solved in the next decade ;-)