Protocol Buffers Google Group

Re: 2.0.2 release is up

2008-10-08T05:05:38Z

What works is adding to the definition of class DescriptorBuilder to
line1696,

void AllocateOptions(
const typename FileDescriptor::OptionsType& orig_options,
FileDescriptor* descriptor);

And changing the implementation, removing the template specialization,
at line 2213 to:

Re: Solaris 10 Compile problem

2008-10-07T22:15:56Z

Hi Chad,
First, please be aware that protobuf@googlegroups.com is a public mailing
list with non-Googlers on it. If you need to communicate anything
confidential or Google-specific, please e-mail the appropriate internal
mailing list.
Anyway, I'm afraid you're going to have to help out with this, as I do not

Solaris 10 Compile problem

2008-10-07T21:51:21Z

Howdy -
I'm an SA (from doubleclick) working with some former doubleclick and other
google folx trying to get some things set up to xfer between legacy dclk and
google.
They requested that I install protobuf on a couple of hosts, but I'm having
some problem with the make check, and was hoping you could help.

Re: Status of C# Projects?

2008-10-07T21:19:25Z

Thanks for the responses! We are using protocol buffers heavily now...
I might be able to round up some C# developers to test one of those
implementations... no promises, but if I do I will make another post.

Ben

Re: Default values - escaping

2008-10-07T19:43:21Z

We use C-style escaping in both the .proto language and TextFormat. The
only difference from C string literals is that the outer quotes may be
either single or double quotes (as long as they match).

Re: Default values - escaping

2008-10-07T17:45:47Z

Here's the relevant part of the grammar I wrote a while back:

strLit ::= quote ( hexEscape | octEscape | charEscape | /[^\0\n]/ )*
quote

quote ::= /["']/

hexEscape ::= /\\[Xx][A-Fa-f0-9]{1,2}/

octEscape ::= /\\0?[0-7]{1,3}/

charEscape ::= /\\[abfnrtv\\\?'"]/

Though it might have changed by now.

Re: Unittest failure in python decoder tests

2008-10-07T16:53:53Z

int vs long is a python 2.x annoyance. It goes away in 3.x as the int
vs long distinction disappears.
Regardless, the correct thing to do in 2.x is to accept both int and
long types, this unit test is being too strict. What matters is the
actual value, not the exact type. In decoder_test.py
ReadScalarTestHelper line 107 the following assertion is too strict:

Re: question about c# CLR library for c++

2008-10-07T16:50:53Z

For reference
[link]

Marc

Re: question about c# CLR library for c++

2008-10-07T16:22:20Z

I think you're likely to have better luck with one of the unfinished
but basically working .NET implementations which already exist. Have
you tried any of them yet?

Jon

question about c# CLR library for c++

2008-10-07T15:47:40Z

hi,
since protobuf has no C# yet, i tried to use CLR C++ and use C# to
call them, unfortunately, it failed.

i created a .net CLR Library by using pb.h and pb.cc, it builded
success.
Then add the .lib to another C# project as reference, but it occurs
link error, the class and functions can not be linked.

Default values - escaping

2008-10-07T12:05:58Z

It doesn't seem explicit in the language guide - what escaping should
be applied to default strings that contain quotes?

Cheers,

Marc

Re: 2.0.2 release is up

2008-10-07T11:27:21Z

Nope - same error...

Any other ideas?

Re: Unittest failure in python decoder tests

2008-10-07T10:29:11Z

From python docs at [1]:
Plain integers (also just called integers) are implemented using long in
C, which gives them at least 32 bits of precision (sys.maxint is always
set to the maximum plain integer value for the current platform, the
minimum value is -sys.maxint - 1).
Since python lacks 'unsigned int' it's represented as long.

Re: Unittest failure in python decoder tests

2008-10-07T09:22:46Z

Problem is in struct.unpack function
Unpacking "<I" (wire_format.FORMAT_UINT32_LIT TLE_ENDIAN) on 32 and
64 bit systems give different types.
$ uname -m
i686
$ python -c 'import struct; print type(struct.unpack("<I", "\xff\xff\xff\xff")[0])'
<type 'long'>
$ python --version
Python 2.5.2
$ uname -m
x86_64

Re: Can a text formated "Flat file" be parsed to PB message given the format of message in .proto file?

2008-10-07T04:34:05Z

Indeed It helped a lot Varda. Thank you for the input. I guess I need
to explore more. I wonder what else can be done with PBs. :)