Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support for nested definitions in .proto files #5

Open
acg opened this issue Nov 25, 2011 · 0 comments
Open

support for nested definitions in .proto files #5

acg opened this issue Nov 25, 2011 · 0 comments

Comments

@acg
Copy link
Owner

acg commented Nov 25, 2011

Currently, the python lwpb code can't resolve nested definitions like this:

 message A {
   message B {
     enum C {
     ...
     };
   };
 };

 message D {
   optional A.B.C stuff = 1;
 };

The rules for resolving type names follow C++ scoping.

This feels like an unnecessary complication in the protocol buffers spec -- I've personally never had a need for it and simply use a flat list of definitions in my .proto files.

However, it's in the spec, so see if it can be implemented in the descriptor code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant