We changed the typedefs because with the old definition protobuf code does
not build on platforms where int32_t is defined to be long. I can see how
the new definition causes issues on platforms where int64_t is not long
long though. Could you submit an issue for this on our github site?

On Wed, Sep 23, 2015 at 12:17 PM, Chinmaya <chinmaya...@gmail.com> wrote:

> Hello Guys, One of the changes in the latest proto3 library is that the
> following typedefs are changed from
>
> typedef int64_t int64;
>
> typedef uint64_t int64;
>
>
> to
>
>
> typedef long long int64;
>
> typedef unsigned long long uint64;
>
>
> Could you let us know the reason for this change. In our codebase we have
> int64_t & uint64_t based typedefs and some of the things becomes
> incompatible with the newest definitions. Google logging library also as it
> as int64_t based typedef.
>
> Thanks
> Chinmaya
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to