summaryrefslogtreecommitdiff
path: root/test/EnumTest.thrift
Commit message (Collapse)AuthorAgeFilesLines
* THRIFT-3921: Add ostream operator<< functions for enums (working with ↵Vivek Jain2017-02-181-0/+5
| | | | | | | | | THRIFT-4060) Client: C++ This closes #1083 This closes #1194
* THRIFT-3477 Parser fails on enum item that starts with 'E' letter and ↵Jens Geyer2015-12-081-0/+5
| | | | | | | continues with number Client: Compiler (general) Patch: Jens Geyer
* THRIFT-3464 Fix several defects in c_glib code generatorNobuaki Sukegawa2015-12-061-0/+37
| | | | | | | Client: c_glib compiler Patch: Nobuaki Sukegawa This closes #724
* THRIFT-2784 Eliminate compiler warnings in generated C++ codeRoger Meier2014-10-211-6/+0
| | | | remove unused MyEnum5 and add -pedantic to lib/cpp/test/Makefile.am
* THRIFT-2513 clean up enum value assignmentJens Geyer2014-09-121-0/+8
| | | | | Client: Compiler (General) Patch: Jens Geyer
* THRIFT-2513 clean up enum value assignmentJens Geyer2014-09-041-0/+70
Patch: Dave Watson This closes #88 Summary: Clean up how enum values are handled if an integer value is not explicitly specified in the thrift file. For example, the following used to be a compile error, but works now: enum MyEnum { SOMEVALUE } struct MyStruct { 1: MyEnum e = SOMEVALUE } This change also cleans up some of the error handling with out-of-range values. Previously thrift simply issued a warning for enum values that didn't fit in an i32, but serialized them as i32 anyway. Now out-of-range enum values result in a compile failure. Test Plan: Included a new unit test to verify the assignment of enum values. I also verified that g++ makes the same enum value assignments when compiling these enums as C++ code.