- 11 Jan, 2018 1 commit
-
-
Kenton Varda authored
@kloepper pointed out a while back that every compiler you've ever heard of supports this. Plus, it's more concise, it's not prone to copy-paste errors, and it looks nicer. At the time I wanted to remain consistent and I didn't feel like spending the time to update all my existing code. But, every time I've added a new header since I've cursed the include guard, so I finally broke down and changed it.
-
- 25 Apr, 2017 1 commit
-
-
Kenton Varda authored
Fixes #336
-
- 07 Apr, 2017 1 commit
-
-
Kenton Varda authored
-
- 18 Nov, 2016 1 commit
-
-
Kenton Varda authored
-
- 02 Apr, 2016 1 commit
-
-
Liam Staskawicz authored
fixes #304
-
- 23 Jul, 2015 1 commit
-
-
Kenton Varda authored
Fix bug causing exception: "'Disembargo' of type 'senderLoopback' sent to an object that does not point back to the sender." The problem happened when pipelined calls were made on a promised capability, but then that capability turned out to be null. The promise resolving code incorrectly interpreted this as the remote promise having resolved to a local capability (because the "null" stub capability looks local), and so it would send a Disembargo message to flush the pipeline as required. However, the remote end would receive this Disembargo message and find it is addressed to a null capability, not a capability pointing back to the sender. This was treated as a protocol error, causing the receiver to close the connection. The solution is to explicitly identity "null" capabilities so that we can distinguish this case. This change also has the benefit that now when you copy a null capability between messages with foo.setCap(bar.getCap()), the pointer will be set null in the destination, rather than becoming a reference to a local broken capability. Thanks to David Renshaw for narrowing this down.
-
- 22 Mar, 2015 1 commit
-
-
Kenton Varda authored
Fix but where interface server's transitive superclass's methods weren't dispatched correctly -- ouch.
-
- 30 Dec, 2014 1 commit
-
-
Kenton Varda authored
A compatibility layer is provided to ease migration.
-
- 29 Nov, 2014 1 commit
-
-
Kenton Varda authored
Add asBytes() and asChars() methods to array classes to reinterpret-cast to bytes / chars, since this happens all the time and is otherwise a huge pain. Use the new methods in a bunch of places.
-
- 24 Nov, 2014 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
The project file still only compiles a test binary, but it should be easy to separate out a library project from here. Thanks again to Bryan Boreham <bjboreham@gmail.com> for much help getting this working.
-
- 22 Nov, 2014 1 commit
-
-
Kenton Varda authored
This prevents the compiler from reporting warnings in these headers while compiling application code. Hopefully this will stem the never-ending stream of complaints from people who enable pedantic warnings.
-
- 26 Oct, 2014 1 commit
-
-
Kenton Varda authored
To use, pass --disable-reflection to the configure script. This produces a smaller runtime library. However, using it for this purpose is not recommended. The main purpose of lite mode is to define a subset of Cap'n Proto which might plausibly compile under MSVC. MSVC still lacks full support for constexpr and expression SFINAE; luckily, most of our use of these things relates to reflection, and not all users need reflection. Cap'n Proto lite mode inherits its name from Protocol Buffers' lite mode. However, there are some key differences: - Protobuf generated code included global constructors related to registering descriptors and extensions. For many people, this was the main reason to use lite mode: to get rid of these global constructors and achieve faster startup times. Cap'n Proto, on the other hand, never had global constructors in the first place. - Schemas are actually still available in lite mode, though only in their raw (Cap'n Proto structure) form. Only the schema API (which wraps the raw schemas in a more convenient interface) and reflection API (which offers a convenient way to use the schemas) are unavailable. - Lite mode is enabled in an application by defining CAPNP_LITE rather than by specifying an annotation in the schema file. This better-reflects real-world usage patterns, where you typically want to enable lite mode application-wide anyway. - We do not build the lite mode library by default. You must request it by passing --disable-reflection to the configure script. Before you can do that, you must have a prebuilt Cap'n Proto compiler binary available, since the compiler can't be built without reflection. - Relatedly, the lite mode library is built with the same name as the full library. This library is not intended to be installed. If anything it should be statically linked. But, mostly the option only exists on non-MSVC platform to give us a way to test that we haven't broken lite mode.
-
- 11 Sep, 2014 1 commit
-
-
Kenton Varda authored
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.
-
- 20 Jun, 2014 1 commit
-
-
Kenton Varda authored
For portions currently copyright by Kenton (most of it), transfer copyright to Sandstorm Development Group, Inc. (Kenton's company). The license change is practically meaningless, as MIT and BSD 2-clause are legally equivalent. However, the BSD 2-clause license is sometimes confused for its ugly siblings, BSD 3-clause and BSD 4-clause. The MIT license is more immediately recognizeable for what it is. Rémy Blank and Jason Choy (the two non-trivial contributors) are on record as approving this change: https://groups.google.com/d/msg/capnproto/xXDd2HUOCcc/gbe_COIuXKYJ
-
- 07 Dec, 2013 1 commit
-
-
Kenton Varda authored
-
- 06 Dec, 2013 1 commit
-
-
Kenton Varda authored
-
- 05 Dec, 2013 1 commit
-
-
Kenton Varda authored
Get rid of 'Advanced' server methods, just have one method that takes a CallContext. A typedef reduces boilerplate.
-
- 26 Nov, 2013 2 commits
-
-
Kenton Varda authored
Implement opt-in cancellation for local calls. (Previously, cancellation would happen whether or not the callee had opted in.)
-
Kenton Varda authored
-
- 25 Nov, 2013 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
-
- 23 Nov, 2013 1 commit
-
-
Kenton Varda authored
Tail calls half-implemented, but I think it's time to delete all the cancellation code before continuing because it will simplify things.
-
- 08 Nov, 2013 1 commit
-
-
Kenton Varda authored
Implement two-party network. The first RPC call over a socket took place at 2013-11-08 14:46:43 -0800 and completed successfully.
-
- 08 Jul, 2013 1 commit
-
-
Kenton Varda authored
-
- 24 Jun, 2013 1 commit
-
-
Kenton Varda authored
-
- 06 Jun, 2013 5 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
-
Kenton Varda authored
-
Kenton Varda authored
-
Kenton Varda authored
-
- 05 Jun, 2013 1 commit
-
-
Kenton Varda authored
-
- 22 May, 2013 1 commit
-
-
Kenton Varda authored
-
- 04 May, 2013 1 commit
-
-
Kenton Varda authored
Delete Code Friday: Inline structs/lists/data are too complicated for not enough benefit. There goes a week of my life that I'll never get back.
-
- 27 Apr, 2013 1 commit
-
-
Kenton Varda authored
-
- 25 Apr, 2013 1 commit
-
-
Kenton Varda authored
-
- 20 Apr, 2013 1 commit
-
-
Kenton Varda authored
-
- 19 Apr, 2013 1 commit
-
-
Kenton Varda authored
-
- 29 Mar, 2013 1 commit
-
-
Kenton Varda authored
-
- 28 Mar, 2013 1 commit
-
-
Kenton Varda authored
-