Comment #13 on issue 83 by halostatue: protobuf does not compile cleanly in
64-bit mode in Visual Studio 2008
http://code.google.com/p/protobuf/issues/detail?id=83
Yeah, it's a little ugly, but it's consistent with what I've seen in gtest.
The problem with the truncating_cast as
you've spec
Thanks
It looks like there is no elegant way to solve my issue.
In short, I have a transport implementation to use with PB RPC
service.
Service definitions are built-in and I need to convert byte array to
Message inside my transport. I know what service transport handles and
I have method name.
Se
Comment #12 on issue 83 by ken...@google.com: protobuf does not compile
cleanly in 64-bit mode in Visual Studio 2008
http://code.google.com/p/protobuf/issues/detail?id=83
Yikes, adding #pragmas all over like that is pretty ugly.
What is the proper way to prevent these warnings in MSVC, witho
(But to answer your question: Compiled-in types are almost always faster
than DynamicMessage.)
On Tue, Feb 23, 2010 at 4:27 PM, Kenton Varda wrote:
> I'm not sure how your approach works, but since it looks like you're using
> Java reflection, my guess is that it will only work with compiled-in
I'm not sure how your approach works, but since it looks like you're using
Java reflection, my guess is that it will only work with compiled-in
services. If your code is a library, this will prevent users of that
library from using dynamic types, which is unfortunate. If the users
provide a defau
Comment #7 on issue 158 by jasonab: Push 2.3.0 maven artifact to repo
http://code.google.com/p/protobuf/issues/detail?id=158
The artifact is now in the maven central repository, although not in the
Google
repository.
--
You received this message because you are listed in the owner
or CC fiel
Thanks Kenton,
I was using getRequestPrototype, but I need an actual instance of
Service to call that method that created additional extra dependency
in my code that why I started to look for alternatives. I know my
method name and currently I'm just parsing response (byte array) this
way (in Scal
I got protobuf to build on Solaris 8. All tests are passing on sparc
(both 32 and 64-bit), two tests are failing on i386. (amd64 build is
yet to come)
[ FAILED ] CommandLineInterfaceTest.OutputDirectoryIsFileError
[ FAILED ] DiskSourceTreeTest.MapDirectory
[ RUN ] DiskSourceTreeTest.M
