- 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.
-
- 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.
-
- 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
-
- 02 May, 2014 1 commit
-
-
Kenton Varda authored
Add ability to truncate a list post-allocation and reclaim space. Currently limited to blobs and can only be accessed through the Orphan interface.
-
- 12 Mar, 2014 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
Make it possible for a message builder to incorporate a byte array not owned by it without copying. Useful for injecting large data blobs into a message without copying their contents. Access this functionality through the Orphanage interface.
-
- 07 Dec, 2013 1 commit
-
-
Kenton Varda authored
-
- 05 Dec, 2013 1 commit
-
-
Kenton Varda authored
-
- 12 Nov, 2013 1 commit
-
-
Kenton Varda authored
Allow implicit conversion from Orphan<T> to Orphan<DynamicStruct/DynamicList/DynamicCapability> where applicable.
-
- 24 Sep, 2013 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
Revamp generated interface to Object fields. Now there is an ObjectPointer::{Reader,Builder}. This will simplify the dynamic API (next change) and also makes it easier to delegate decisions about the object type to a function that doesn't know about the context where the object lives (i.e. by passing an ObjectPointer::Builder).
-
- 31 Aug, 2013 1 commit
-
-
Kenton Varda authored
Actually fix the bug, which was a doozy: OrphanBuilder::tag was sometimes initialized using WirePointer::setKindAndTarget(), but since the tag didn't live inside the target segment, this used illegal pointer arithmetic. The target is never read from an orphan tag anyway, so I thought it would be no big deal. But it turns out Clang actually optimizes under the assumption that pointer arithmetic returns a whole value. As a result, on 32-bit system where 64-bit values are only 32-bit aligned, the tag and target might not have been a whole number of words apart, and the extra bit actually found its way into the 'kind' bits, causing e.g. a struct pointer to become an invalid far pointer. Crash. The fix required refactoring to ensure that setKindAndOffset() is never used for orphan tags.
-
- 26 Aug, 2013 2 commits
-
-
Kenton Varda authored
-
Kenton Varda authored
-
- 14 Aug, 2013 1 commit
-
-
Kenton Varda authored
-
- 18 Jul, 2013 1 commit
-
-
Kenton Varda authored
-
- 15 Jul, 2013 1 commit
-
-
Kenton Varda authored
-
- 09 Jul, 2013 1 commit
-
-
Kenton Varda authored
-
- 08 Jul, 2013 1 commit
-
-
Kenton Varda authored
-