On Wed, Nov 7, 2018 at 4:28 PM Michael Powell <[email protected]> wrote: > > Hello, > > Is there some documentation concerning import semantics? > > For starters, I assume that you specify the path. This may be further > enhanced by specification of an "import path", not unlike in C++ > wherein you may specify include, library, etc, paths.
I have not received any clarification for this. Can someone please clarify? I want to think in terms of C++ access modifiers, private, protected, public, etc, but I'm not positive this is analogous, or what the ramifications ought to be when "linking" across .proto files. http://developers.google.com/protocol-buffers/docs/reference/proto2-spec#import_statement > Second, what is the impact of "weak"? "public"? Or an unspecified modifier? > > Thanks! > > Best regards, > > Michael Powell -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
