Re: [protobuf] protogen golang - finding source line for diagnostics?

dev/google.golang.org/protobuf/compiler/protogen#Location> > type looks promising. > > On Thu, Nov 3, 2022 at 3:07 AM Steve Simon wrote: > >> Hi, >> >> I am using protogen for go successfully. We are using >> extend google.protobuf.ServiceOptions { as we ne

[protobuf] protogen golang - finding source line for diagnostics?

Hi, I am using protogen for go successfully. We are using extend google.protobuf.ServiceOptions { as we need to encode extra fields for our backend. When I find typos in the serviceOptions I am parsing I would like to generate diagnostics which reference the source proto file and line number.

[protobuf] protogen - creating python code from a go plugin?

Hi. We use protobufs with NATS and have added structured comments to our .proto files to describe the NATS topic and transaction style we use for a particular protobuf Message. I have a protogen plugin to generate RPC stubs for go but we would like to generate similar RPCs for python (for our

[protobuf] Re: Rust protobuf support

to re-generate the protobuf implementation as well as the Rust code that uses it. I hope this helps. Simon On Sunday, August 8, 2021 at 1:31:44 PM UTC-4 yimeng...@gmail.com wrote: > Hi! > > I am trying to use protobuf in my rust actix server. There is this library > https://gith

[protobuf] Protobuf keyword list.

Hi all , I want to know all the keywords in .proto file, Is there a keyword list about this ? -- 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] oneof feature example using c++

it. essage Message1 { string a = 1; string b = 2;} message Message2 { int64 id = 1; string data = 2;} message WrapperMessage { oneof msg { Message1 m1 = 2; Message2 m2 = 3; } } rgds Simon -- You received this message because you are subscribed to the Google

Re: [protobuf] Embedded message compression

Thanks for your reply, I already found why it doesn't work: uint32 in proto file is converted in varint in line... So I changed uint32 to fixed32 but a second question happen: How to force enum to be a fixed32 and not a uint32 (converted in varint)? Le mardi 30 juillet 2019 23:46:08 UTC+2,

Re: [protobuf] What version of protobuf builds with -std=c++98 or -std=c++03?

On Monday, July 8, 2019 at 11:05:53 PM UTC+1, Adam Cozzette wrote: > > The 3.5.x branch contains the most recent code that still builds without > requiring C++11. > I've tried 3.5.1 and 3.5.2 and both require va_copy which is C++11 and later. -- You received this message because you are

[protobuf] What version of protobuf builds with -std=c++98 or -std=c++03?

In https://github.com/protocolbuffers/protobuf/issues/2780 it's suggested that "We may create a branch that works for C++98. The branch will only accept bug fixes, but not new features, optimization, etc" https://github.com/protocolbuffers/protobuf/issues/3492 "Code should compile with

[protobuf] proto3 hasField return error

public class Test { public static void main(String[] args) throws Exception { Device device = Device.newBuilder() .setMeterAperture(0) .build(); // device.getMeterAlarm(); System.out.println(device.hasField(Device.getDescriptor().findFieldByNumber(Device.METER_APERTURE_FIELD_NUMBER))); // PRINT

[protobuf] 2.6.0rc1 fails to build on mac 10.9

more testing. Simon -- 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

[protobuf] Re: 2.6.0 release candidate

nobase_include_HEADERS. Simon Thanks, Jie -- 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

Re: [protobuf] 2.6.0 release candidate

On Thu, Aug 21, 2014 at 8:49 AM, Simon Newton si...@nomis52.net wrote: I get a build failures on Mac OS X 10.9: Sorry please ignore that, I was building the wrong RC. Simon $ g++ --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr

Re: [protobuf] 2.6.0 release candidate

I get a build failures on Mac OS X 10.9: $ g++ --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) Target: x86_64-apple-darwin13.3.0 Thread model: posix I

[protobuf] Problem with accent

Hi guys, I have an annoying problem with some accent. I build my proto-object, no problem, and when i want to read it the browser, using .toString function, i have \303\240 instead of à, \303\250 instead of è, etc... So i'm wondering where can be the problem ? Eclipse encode the files in UTF-8,

Re: [protobuf] different results parsing from string in Java and Python

Thanks, that fixed the problem. On Sun, Feb 28, 2010 at 11:44:53PM -0800, Kenton Varda wrote: 2.0.3 is pretty old, and I think it had an endianness issue in Python. Use 2.3.0 instead. On Sun, Feb 28, 2010 at 5:33 PM, metapieman s.d.c.w...@googlemail.comwrote: Hi, I'm having a