Naming convention in C# constructor is not consistent with other fields causes
compile errors
---------------------------------------------------------------------------------------------
Key: THRIFT-992
URL: https://issues.apache.org/jira/browse/THRIFT-992
Project: Thrift
Issue Type: Bug
Components: C# - Compiler
Affects Versions: 0.5
Environment: Using the windows binary release of thrift-0.5.0.exe on
Windows 7 64-bit
Reporter: Nick Berardi
Priority: Blocker
While updating my FluentCassandra project using the latest Thrift-0.5.0.exe
generator against the 0.7 Beta3 release of cassandra.thrift I experienced a
generation problem that caused compiler errors when compiling the C# code. It
appears the constructor fields are using the old naming convention for the
fields, while every other part of the class seems to be using the new naming
convention for fields with underscores.
You can see a diff of the files I had to manually edit here:
https://github.com/managedfusion/fluentcassandra/commit/d2d26f0bfd158cae3c39fd9cd47ec9097bc394f6
The paths starting with "FluentCassandra/Apache/Cassandra" should be the ones
that you need to worry about for this bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
