[protobuf] Re: Issue 487 in protobuf: Building failure with clang or scan-build

2013-03-20 Thread protobuf


Comment #1 on issue 487 by chen3feng: Building failure with clang or  
scan-build

http://code.google.com/p/protobuf/issues/detail?id=487

FYI:
~/scan-build/bin/clang -v
clang version 3.2 (trunk 157010)
Target: x86_64-unknown-linux-gnu
Thread model: posix

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups Protocol 
Buffers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[protobuf] Issue 487 in protobuf: Building failure with clang or scan-build

2013-03-20 Thread protobuf

Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium

New issue 487 by chen3feng: Building failure with clang or scan-build
http://code.google.com/p/protobuf/issues/detail?id=487

What steps will reproduce the problem?
1. build the code with clang or scan-build

What is the expected output? What do you see instead?
./thirdparty/protobuf-2.3.0/src/google/protobuf/wire_format_lite.h:292:48:  
error: parameter declarator cannot be qualified

  static bool ReadBytes (io::CodedInputStream* input, string* value);
   ^
./thirdparty/protobuf-2.3.0/src/google/protobuf/wire_format_lite.h:233:19:  
note: expanded from macro 'input'

#define input io::CodedInputStream* input
  ^

What version of the product are you using? On what operating system?
2.3.0, but 2.5.0 is still has this problem.

Please provide any additional information below.

Attachments:
issue31351_46283_399040.diff  706 bytes

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups Protocol 
Buffers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[protobuf] Re: Python3 Protobufs

2013-03-20 Thread Malthe Borch
I have completed this work: https://github.com/malthe/google-protobuf.

– in as much as that all tests run without fail on both 2.7 and 3.3. I have 
used a single-source approach (which is only really feasible starting with 
those two for syntax compatibility reasons).

Python 2.4, 2.5 and I believe even 2.6 simply aren't going to work. It's 
too much effort.

\malthe

On Saturday, September 22, 2012 3:16:41 AM UTC+2, Charles Law wrote:

 I've made an attempt to create a Python3 compatible version of protobufs. 
  I have some code that passes pretty much all the unit tests which I've 
 posted here:

 https://github.com/openx/python3-protobuf

 I probably won't have a chance to look at this again for a couple weeks if 
 not longer, so I want to get it out there.  In my attempt I decided to 
 follow the advice in another post, and treat python3 as a new language.  To 
 get python3 working, you'll have to compile the C code.  There are also a 
 few issues I ran into along the way:

- I decided to use strings where unicode is used in Python 2.  I was 
originally going to try to use bytes/bytearrays, but they do not support 
 8 
bit characters, and some of the setup.py tests use exotic 16 bit chrs. 
(Warning: I might have something conceptually wrong here)
- There are places where byte data is stored as strings, then 
converted to unicode.  I ended up converting strings (I called them 
bytestr's) to normal strings.  I'm not sure this is done correctly 
everywhere though.
- Data is packed/unpacked using struct.pack/unpack which is done using 
bytes instead of strings in Python3.  I have simple string_to_bytes() and 
bytes_to_string() functions to do this.


 What's left is:

- There are a couple Exceptions that I don't throw.  They are supposed 
to be where the Python2 code converts from unicode strings to regular 
strings.  I am definitely missing something conceptually here - I haven't 
figured out how Python 2x supports strings with exotic characters, but 
not strings like u'a\x80a'.  If someone can solve this problem  figure 
 out 
when to throw the exceptions Python3 will be *fully* working.


 I might have small bits of time here or there but I don't think I can 
 devote the time I need to get this finished for several weeks, so if 
 someone wants to finish this up, feel free to fork this code.  If anyone 
 wants to see what I did, the best way to do this is to diff between the 
 latest commit and commit 49ccf5d8b3b688c335dc35bcb9f219eca78c7210.
 Thanks!
 Charles


-- 
You received this message because you are subscribed to the Google Groups 
Protocol Buffers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[protobuf] C++, RPC, Linux server, windows client

2013-03-20 Thread Damian
Is there a nice implementation of an RPC server that runs on Linux and has 
a client for Windows.
It should use protcolbuf for messages.
All code is C++.

The only examples I can find all compile well on Linux but do not have so 
much luck on Windows!

I checked  all these 
https://code.google.com/p/protobuf/wiki/ThirdPartyAddOns


-- 
You received this message because you are subscribed to the Google Groups 
Protocol Buffers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.