But the type stored on the wire is known - so it seems like it could be
supported (simply static_cast(float_val)). By 'some libraries':
does the C++ ParseFromString method do this or not?
Thanks!
James
On Wed, Nov 15, 2017 at 3:57 PM Marc Gravell wrote:
> Not really,
Hi,
Is it possible to saving out the message into a file with unicode name? Say
some Chinese or German characters in the file name? I only saw two APIs in
the message.h's document,
bool Message::SerializeToFileDescriptor(
int file_descriptor) const
Serialize the message and write it
Not really, no. They take different amounts of space on the wire, and have
a different declared wire type (header). Some libraries may choose to be
gracious and apply the conversion silently, but other libraries could just
say "unexpected wire type" and stop processing.
You could perhaps do it as
Hi,
Is it safe to upgrade float fields to doubles for serialized protos? If
not, why not?
Thanks,
James
--
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
Can you create an issue for this on https://github.com/google/protobuf ?
On Wed, Nov 15, 2017 at 6:26 AM,
wrote:
> Tho following 3 issues were flagged by a security scan where we use
> Protobuf v3.4.0. Will these be resolved in an upcoming version?
>
>
>
Tho following 3 issues were flagged by a security scan where we use
Protobuf v3.4.0. Will these be resolved in an upcoming version?
1. Unchecked CString Convertion
The element Param at line 273 of /Protobuf/objectivec/GPBCodedOutputStream.m
contains a C-String that was converted from a