Update blog post to reflect that FlatBuffers now supports optional bounds checking.
Add configured includedir as a default import path

Protected by an ifdef to avoid tripping up non-autotools builds
Support for exception backtraces on OS X.
Merge pull request #109 from greedy/add-includedir-to-imports

Add configured includedir as a default import path
Consolidate Linux and OS X versions of getStackSymbols().
Replace 'goto' error handling with KJ_DEFER.
Merge pull request #111 from partylemon/ExceptionBacktraces

Support for printing exception backtrace symbols on OS X.
Fix typo. Fixes #112.
Merge branch 'master' of github.com:kentonv/capnproto
Fix two subtle bugs with embargos, and improve docs.

Bug 1
-----

If a Resolve message indicated that the promise had been rejected, the code would see the error cap as a local cap and erroneously believe that the promise had resolved back to a local capability, thereby requiring a Disembargo to be sent. The peer, on receiving the nonsensical Disembargo, would throw an exception and close the connection.

The error message seen was: "expected target->getBrand() == this; 'Disembargo' of type 'senderLoopback' sent to an object that does not point back to the sender."

Bug 2
-----

Disembargos are sent not only in response to Resolves, but also Returns, since capabilities in a returned message were previously accessible as PromisedAnswers. This means that we must apply the same rule that states that once a promise has been resolved, the promise must from then on forward all messages it receives strictly to the object to which it resolved, even if that object is itself a promise which later resolves to somewhere else. The code which sends Resolve messages was doing this correctly, but the code sending Return messages was not. They now both operate correctly. I've also added more explanation to the documentation in rpc.capnp.

The error message seen was: "expected redirect == nullptr; 'Disembargo' of type 'senderLoopback' sent to an object that does not appear to have been the object of a previous 'Resolve' message."
Add missing implementation of rejectIfThrows().
Fix typo
Replace AC_PROG_LIBTOOL with LT_INIT in configure.ac

AC_PROG_LIBTOOL is a deprecated name for older versions of LT_INIT.[1]

1. http://www.gnu.org/software/libtool/manual/html_node/LT_005fINIT.html
Merge pull request #116 from mortehu/master

Replace AC_PROG_LIBTOOL with LT_INIT in configure.ac
Merge pull request #114 from puls/patch-1

Fix typo
Fix link to 'Capability Myths Demolished' paper

The old link isn't currently working.
Merge pull request #117 from dharmatech/patch-1

Fix link to 'Capability Myths Demolished' paper
Fix another case of Capability Myths Demolished link.
Merge branch 'master' of github.com:kentonv/capnproto
Fix obscure bug where the last outgoing message (and any capabilities therein) would not get released (until a new message was sent, replacing it as the last).

This took hours to track down, because it initially looked like "Release" messages weren't being honored in some cases (when they happened to be releasing a capability from the last message, and no subsequent messages were sent). Initial attempts to capture this in a unit test failed because the test of course used a subsequent call to detect if the capability had been released, which succeeded.