This allows you to have binary data imported into your application via
strings instead of arrays of numbers! This needs testing before release.

This does not (should not) change behavior.  Pulls those two functions
(encode/decode) out into node.cc.

This completes shebang support begun in
6acac912.

They were deprecated in 723c7d9f and
31265be4.

Still retaining error message.

I don't have access to this OS to fix the issue properly, so for the moment
I'm reverting back to 32bit build on Darwin. We changed to native 64bit in
8ddf9309.

Thanks to Johan Dahlberg and Tim Caswell for reporting and debugging this.

A user was able to crash chat.tinyclouds.org by sending it a malformed URL!
Not good.

I'm not sure what is actually causing

  node_g test/mjsunit/test-tcp-many-clients.js

to run slowly, but I traced the problem to
afd9e714.
Somehow it has to do with promoting the compilation of src/util.js. That
change wasn't actually intended to be included in afd9e7 commit anyway, so
I'm reverting it here.

64kb seems to be the magic number for getaddrinfo() to work on Macintosh.

The problem was that if promise A was waiting and promise B was created and
then also told to wait (from some callback coming off the event loop), and
then promise A finished, promise B's wait would return. Promise A's wait
would not return until promise B was finished. This is incorrect.

To solve this issue properly, one probably needs to allocate separate
execution stacks. I use, instead, Poor Man's Coroutines. We continue to use
the main execution stack and force promises created most recently to return
first.

That is even if Promise A finishes first, neither wait() returns. Not until
Promise B finishes, will its wait() return. After that is complete, Promise
A's wait() will return.

This introduces the problem of growing the "wait stack" infinitely. Thus
I've added a strong warning to the documentation only to use this operation
sparingly. require() and include() seem to be the proper use case for such a
thing: they are called usually at program start up - they don't take too
long to finish and they won't be called so often.

Let's experiment with this stop-gap. If the infinite promise stack becomes a
problem for many, then I will remove promise.wait() entirely or perhaps only
use it for thread pool events.

Had to add some waf hackery to override V8's architecture choice. They
probably have a reason for defaulting still to IA32, but all tests are
passing for me, and it makes it easier on users-and I think chrome is using
x64 builds too. So let's go for it!

Not necessary to build dll modules after all.

The error reporting function tries to look at the "stack" element of the
exception.

The default timeout is 60 seconds, but it can now be changed.

evcom upgrade includes fixes to force_close.