node: properly destroy drivers, engine and reactor if the initialization went south; this bug never really fired because of another bug in libev, which was locally fixed here
wording
an ability to post async jobs to the reactor (in case when something cannot be done in the handler)
erase slaves asynchronously so that the i/o handler won't execute its last instructions on a deleted object
proper naming and includes
Add new tools
Merge pull request #27 from noxiouz/master

rewritten cocaine tools
Remove c++ tool.
Merge pull request #28 from noxiouz/master

resolve cocaine-tool issues
set slave working dir to spool subdir in process isolate
use boost filesystem's native function to set the current working directory
fs::path::native() is not yet implemented in boost 1.40
hanging dtor tilde styling
hanging dtor tilde styling
Properly generate the version number.

The old version #define was treated as a floating-point number, so
that the 'cocaine-runtime -v' command displayed the current version
as 0.1, which was incorrect. Now the version number is made of three
numbers - major, minor and release - which are combined together to
display the effective Cocaine version.
Merge branch 'master' of github.com:cocaine/cocaine-core
Merged chrono and filesystem plugin drivers.

Chrono and filesystem plugins are moved into the core, as they do not
depend on anything except it, so there's no point in keeping them
separate.

Also, recurring timer and drifting timer drivers are refactored into a
simple 'time' driver, because nobody ever used the drifting alternative.
Fixed Clang 3.2 -Wunused-private-field warnings

Clang 3.2 complains on unused private class fields. We build with
-Werror, so now these fields are dropped from the driver classes.
Use the quick exit path on failed execve().

Previously, when an isolate failed to execve() a new worker process, it
terminated the execution of the current forked process with std::exit().
It appeared that because std::exit() invokes the destructors of static,
automatic and thread-local variables, ZeroMQ context object managed to
close its parent process sockets (or do something similiarly bad), which
triggered various asserts in the ZeroMQ core.
Poor man's lambda functions.

Refactored functors a bit to resemble lambda functions more closely.
Does not bring anything useful, only beauty.