Skip to content

support for nested definitions in .proto files #5

@acg

Description

@acg

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions