On Sun, May 17, 2009 at 6:57 AM, Chris Kuklewicz wrote:
>
> I am patching the Haskell implementation and I have a follow up
> question to this:
>
> On May 14, 12:06 am, Kenton Varda wrote:
> > * The type name resolver will no longer resolve type names to fields.
> For
> > example, this now
I am patching the Haskell implementation and I have a follow up
question to this:
On May 14, 12:06 am, Kenton Varda wrote:
> * The type name resolver will no longer resolve type names to fields. For
> example, this now works:
> message Foo {}
> message Bar {
> optional
Kenton Varda wrote:
> Here's the major changes (from CHANGES.txt):
>
> General
> * Repeated fields of primitive types (types other that string,
> group, and
> nested messages) may now use the option [packed = true] to get a more
> efficient encoding. In the new encoding, the entire li
Yep, it's there in Java. I didn't get the chance to add the equivalent
support to C++ or Python yet, but if someone wants to submit a patch, go for
it.
On Thu, May 14, 2009 at 7:27 AM, Antony Dovgal wrote:
>
> On 14.05.2009 18:18, clint.foster wrote:
> > It's very nice to see support in the API
On 14.05.2009 18:18, clint.foster wrote:
> It's very nice to see support in the API for length-prefixed messages
Yes, native support for this kind of feature would be very welcome.
--
Wbr,
Antony Dovgal
--~--~-~--~~~---~--~~
You received this message because yo
It's very nice to see support in the API for length-prefixed messages
and blocking RPC's. Both will reduce the amount of boilerplate code
needed for many protobuf applications.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Good job, Kenton!
Thanks for your efforts.
Ciao,
Peter K.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com
To unsubscribe from
Thanks for releasing!
On Wed, May 13, 2009 at 4:04 PM, Kenton Varda wrote:
> http://code.google.com/p/protobuf/downloads/list
> Aaaand, I just realized that CHANGES.txt still has the release date as .
> :(
> /me is not very good at release engineering.
Good enough, these things happen. Tha
Updated documentation covering all this has been submitted and should go
live in a couple hours.
http://code.google.com/apis/protocolbuffers/docs/overview.html
On Wed, May 13, 2009 at 4:06 PM, Kenton Varda wrote:
> Here's the major changes (from CHANGES.txt):
> General
> * Repeated fields o
Here's the major changes (from CHANGES.txt):
General
* Repeated fields of primitive types (types other that string, group, and
nested messages) may now use the option [packed = true] to get a more
efficient encoding. In the new encoding, the entire list is written
as a single byte
10 matches
Mail list logo
