pomack/thrift4go — pull request #56 by GeertJohan (2012-11-18 13:40:02+00:00)
Title: Enum siblings value names

These commits have effect on the names of enum-properties generated by the thrift go generator
The enum values are constants in a go package, therfore, two enums with the same value names would fail. For instance `SomeEnumOne.ValueName`, `SomeEnumTwo.ValueName` would generate invalid go code. It would generate 2 constants with the same name (`ValueName`) in the same go package.
Whereas in java, the value is accessable through `SomeEnumOne.ValueName`
I've renamed the simple test (generation/interoperability) to have One,Two,Three,Four as value names..
so the enum identifying part is removed (Unefined, Defined). The enum identifying part is now included into the enum value by the go code generator (generates: `const DefinedValue_One`).

Travis-CI build on this commit fails because of problems at Travis-CI (so it seems).