Update: we've got an experiment living in https://github.com/grpc/grpc/pull/10427, but are seeing some significant problems mixing C & C++ in the same .so with our current build system on Mac.
On Tue, Apr 4, 2017 at 6:05 PM Craig Tiller <[email protected]> wrote: > Forwarding a note from the Juniper grpc-c folks: > > As long as the public interfaces for grpc_ and gpr_ libs do not change, > this library is not effected. Applications using this library link with > libgrpc and libgpr. However, one of the reasons for applications to use > libgrpc-c instead of libgrpc++ and generated C++ code is compiler support > for C++11 in their environment. If gRPC core requires a compiler with C++11 > support, they will be stuck with older gRPC release till they migrate to a > latest compiler (which they should eventually). But this project will not > be effected by this change. Thanks for reaching out. > > On Tue, Apr 4, 2017, 3:16 PM Nicolas Noble <[email protected]> wrote: > >> Just like with basically everything else, I'd expect that only when >> exaggerating with the compiler, with excessive templating or code >> generation for instance. C++ in itself doesn't generate more code than C >> for the same piece of code. It's what you do with the code that does. >> >> On Mon, Apr 3, 2017 at 5:51 PM, 'Carl Mastrangelo' via grpc.io < >> [email protected]> wrote: >> >>> Are C++ libraries substantially larger than there C counter parts? >>> Binary size is a serious consideration for Java, perhaps it is for wrapped >>> languages too? >>> >>> On Saturday, April 1, 2017 at 7:34:06 AM UTC-7, Craig Tiller wrote: >>>> >>>> I've created a proposal to allow C++ to be used in gRPC Core here: >>>> https://github.com/grpc/proposal/pull/21. >>>> >>>> I'm especially interested in hearing from folks in environments where >>>> this won't work well. >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "grpc.io" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/grpc-io. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/grpc-io/c8ba5869-d372-4215-a5a5-2b492354b2a3%40googlegroups.com >>> <https://groups.google.com/d/msgid/grpc-io/c8ba5869-d372-4215-a5a5-2b492354b2a3%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "grpc.io" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/grpc-io. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/grpc-io/CAEvr0PE3qw9_Di1tDTXjkT4S9wa%2ByeypZ55cSoA53rhHy-U-Pw%40mail.gmail.com >> <https://groups.google.com/d/msgid/grpc-io/CAEvr0PE3qw9_Di1tDTXjkT4S9wa%2ByeypZ55cSoA53rhHy-U-Pw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAAvp3oP7zQAMLJWZ3gC9ggf0V9Hmne%2BrmFQHDfNA6DTtBkONBQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
