On Wed, Feb 23, 2011 at 2:29 AM, Kenton Varda wrote:
> On Tue, Feb 8, 2011 at 4:14 AM, David Yu wrote:
>
>> Hmm, so protoc doesn't handle cyclic imports as well.
>> Are there plans to support it in the near future?
>>
>
> No, cyclic imports are not likely to be supported. Many programming
> lan
On Tue, Feb 8, 2011 at 4:14 AM, David Yu wrote:
> Hmm, so protoc doesn't handle cyclic imports as well.
> Are there plans to support it in the near future?
>
No, cyclic imports are not likely to be supported. Many programming
languages do not support them, so supporting them in .proto would mak
On Tue, Feb 8, 2011 at 6:36 AM, Kenton Varda wrote:
> With protoc (the standard compiler), this should produce a simple error.
> Since Ken said he "got StackOverFlow exception", it sounds like he's using
> some other compiler (not written in C++).
Hmm, so protoc doesn't handle cyclic imports as
On Tue, Feb 8, 2011 at 8:04 PM, Ken wrote:
> I am using protostuff-maven-plugin 1.0.0.M7. Currently I have to put
> all classes into one big proto file. multiple .proto files can't avoid
> cross referencing
>
You're posting in the wrong googlegroups :-)
Might wanna file a bug report on the google
I am using protostuff-maven-plugin 1.0.0.M7. Currently I have to put
all classes into one big proto file. multiple .proto files can't avoid
cross referencing
On Feb 7, 10:36 pm, Kenton Varda wrote:
> With protoc (the standard compiler), this should produce a simple error.
> Since Ken said he "go
With protoc (the standard compiler), this should produce a simple error.
Since Ken said he "got StackOverFlow exception", it sounds like he's using
some other compiler (not written in C++).
On Mon, Feb 7, 2011 at 10:26 AM, Pherl Liu wrote:
> You probably need to break up your proto files to eli
You probably need to break up your proto files to eliminate the circular
dependency.. (i.e. have multiple .proto files for a package, and only import
necessary .proto files).
On Mon, Feb 7, 2011 at 5:42 PM, Ken wrote:
> Hi,
>
> I have two proto files: A.proto and B.proto. If I import package B i
Hi,
I have two proto files: A.proto and B.proto. If I import package B in
A and import A in B, I got StackOverFlow exception during compiling.
Does anyone know any sulotion for it?
Thanks,
Ken
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" grou
On Mon, Sep 28, 2009 at 9:44 AM, Michi wrote:
>
> Hello,
>
> I have defined the following messages:
>
> package myapp.proto.modules.diagnostics;
>
> message DiagnosticsConfigMessage {
>optional bool watchdog_enabled = 1;
>optional uint32 watchdog_timeout = 2;
> }
>
> package myapp.proto;
Hello,
I have defined the following messages:
package myapp.proto.modules.diagnostics;
message DiagnosticsConfigMessage {
optional bool watchdog_enabled = 1;
optional uint32 watchdog_timeout = 2;
}
package myapp.proto;
import "src/myapp/proto/modules/diagnostics/DiagnosticsConfig.prot
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 m
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
12 matches
Mail list logo
