Enum definitions outside of message declared as errors

[GoogleCodeExporter]

Enum definitions outside of message declared as errors

[GoogleCodeExporter]

Tested with:

enum Test {
    MSG1 = 1;
    MSG2 = 2;
}

and works like a charm. 

Send example 'proto' definition that is causing the problem.

Original comment by piotr.tabor on 21 Jun 2010 at 9:13

[GoogleCodeExporter]

I can confirm this bug.
I had this:

.
.
.
enum ReturnType {
  OK = 0;
  FAIL = 1;
}
.
.
.

Original comment by dejan.lekic on 28 Jun 2010 at 9:37

Attachments:

• nb-protobuf-bug002.png

[GoogleCodeExporter]

The problem is not 'enum' support, but  '0' as enum value support. 

It works: 

enum ReturnType {
  OK = 2;
  FAIL = 1;
}

Will fix it. 

Original comment by piotr.tabor on 28 Jun 2010 at 4:20

[GoogleCodeExporter]

True Piotr, thanks for reply and wonderful work! :)

Original comment by dejan.lekic on 29 Jun 2010 at 8:35

[GoogleCodeExporter]

#3 piotr.tabor:
> The problem is not 'enum' support, but  '0' as enum value support.

will this be fixed?
I have lots of enums with 0...

Original comment by [email protected] on 31 Oct 2011 at 1:24