cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4725) VERSION string conflict in C++ programs
Date Fri, 20 Sep 2013 22:36:53 GMT


Jonathan Ellis commented on CASSANDRA-4725:

Doesn't seem like it's worth breaking existing clients to fix this; new clients should use
native protocol instead.
> VERSION string conflict in C++ programs
> ---------------------------------------
>                 Key: CASSANDRA-4725
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jochen Topf
> In cassandra.thrift there is a definition like this:
> const string VERSION = "19.32.0"
> When building the C++ code with thrift, this leads to a file cassandra_constants.h and
cassandra_constants.cpp which contain the following lines:
> cassandra_constants.cpp:  VERSION = "19.32.0";
> cassandra_constants.h:  std::string VERSION;
> Unfortunately "VERSION" is all uppercase, this is generally used in macros in C++ and
the macro "VERSION" is used in many programs for instance when using GNU autoconf. If there
is a VERSION macro it will be expanded and those lines will break.
> Maybe we can rename this to "Version" or so?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message