Sorry, but mutually recursive messages must be declared in a single file.
It would be excessively complicated to support cyclically dependent files
under the current implementation.
On Thu, Aug 13, 2009 at 11:34 AM, Justin Muncaster
justin.muncas...@gmail.com wrote:
I have the following message structure:
===A.proto===
message A
{
optional B1 b1 = 1;
}
message B1
{
optional A a = 1;
}
Everything works as intended when the messages are in the same file.
However, in my situation there are several child messages (B2,
B3, ...) which all naturally all go in their own separate files
(B2.proto, B3.proto, ...). Unfortunately, B1 cannot go in its own file
due to a problem with a recursive import.
Is there any way to solve this? Can I forward declare messages?
Thanks,
Justin
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to protobuf@googlegroups.com
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en
-~--~~~~--~~--~--~---
