Re: [protobuf] Debug assertion failed while attempting to set an object

2013-08-28 Thread Feng Xiao
On Wed, Aug 28, 2013 at 10:31 AM, Rajesh Khan wrote: > > > I currently have something like this. I get an error when i attempt to > store data in a message that has multiple message types in it. > >

[protobuf] Error while attempting to assign a message type as filed in a message type.

2013-08-28 Thread Rajesh Khan
I have something like this in my proto file message MyTypeA { optional string Account = 1 ; optional string Name = 2 ; } message MyTypeB { optional int32 position = 1; } message MyCollection { optional MyTypeA= 1; optional MyTypeB pos = 2; } Now I am using it as *void SomeMethod(MyTypeA&

[protobuf] protobuf_spec: RSpec matchers and Cucumber step defs for testing Protocol Buffers

2013-08-28 Thread Chris Busbey
Hi there! We've just released an open source library for inspecting and building protocol buffers to be used in Cucumber scenarios. Check it out here: https://github.com/connamara/protobuf_spec We think this would be a great addition to the Third-Party Add-Ons wiki (https://code.google.com/

[protobuf] Problem with protobuf class

2013-08-28 Thread michal naz
When i try this: #define PROTOBUF_USE_DLLS #include #include #include #include "profiles.pb.h" using namespace std; using namespace profiles; int main() { profiles::Profile aaa; //fstream in("a1.inp", ios::in | ios::binary); //aaa->ParseFromIstream(&in); return 0; } I have l

[protobuf] Debug assertion failed while attempting to set an object

2013-08-28 Thread Rajesh Khan
I currently have something like this. I get an error when i attempt to store data in a message that has multiple message types in it. message MyTypeA { optional string Account = 1 ; optional strin

[protobuf] Re: Issue 552 in protobuf: PC-Lint accusing errors in atomicops.h and type_traits.h

2013-08-28 Thread protobuf
Comment #3 on issue 552 by xiaof...@google.com: PC-Lint accusing errors in atomicops.h and type_traits.h http://code.google.com/p/protobuf/issues/detail?id=552 I agree with you that maybe __wchar_t is only used by very few people and we don't have to support it. But as you said it's not wro

[protobuf] Re: Issue 552 in protobuf: PC-Lint accusing errors in atomicops.h and type_traits.h

2013-08-28 Thread protobuf
Comment #2 on issue 552 by felipe.f...@gmail.com: PC-Lint accusing errors in atomicops.h and type_traits.h http://code.google.com/p/protobuf/issues/detail?id=552 #define wchar_t __wchar_t is a case that even MS doesn't support, if the user does that MS headers will be inconsistent. They wil

[protobuf] Re: Issue 552 in protobuf: PC-Lint accusing errors in atomicops.h and type_traits.h

2013-08-28 Thread protobuf
Comment #1 on issue 552 by xiaof...@google.com: PC-Lint accusing errors in atomicops.h and type_traits.h http://code.google.com/p/protobuf/issues/detail?id=552 For 1), I think we can change the definition of GOOGLE_PROTOBUF_ATOMICOPS_ERROR to: #define GOOGLE_PROTOBUF_ATOMICOPS_ERROR \ "Ato

[protobuf] Re: Issue 551 in protobuf: changing type of comments to bytes

2013-08-28 Thread protobuf
Updates: Status: WontFix Comment #1 on issue 551 by xiaof...@google.com: changing type of comments to bytes http://code.google.com/p/protobuf/issues/detail?id=551 You should convert your .proto file to utf8 encoding before using protocol compiler to compile it. Protobuf library and

[protobuf] Issue 552 in protobuf: PC-Lint accusing errors in atomicops.h and type_traits.h

2013-08-28 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 552 by felipe.f...@gmail.com: PC-Lint accusing errors in atomicops.h and type_traits.h http://code.google.com/p/protobuf/issues/detail?id=552 When checking a source file that includes the protocol buffer library v2.5.0 wi

[protobuf] Issue 551 in protobuf: changing type of comments to bytes

2013-08-28 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 551 by again1...@gmail.com: changing type of comments to bytes http://code.google.com/p/protobuf/issues/detail?id=551 What steps will reproduce the problem? In descriptor.proto the message Location are defined as