acg/lwpb — Issue #5: support for nested definitions in .proto files
Author: acg
Created: 2011-11-25 19:40:37+00:00
State: open

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](http://code.google.com/apis/protocolbuffers/docs/proto.html#packages).

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.