Problem: inconsistent naming style for private data members, conflicts with naming of local variables and member functions

Solution: apply and check _lower_case naming style for private data members
This commit is contained in:
Simon Giesecke
2018-05-27 11:10:39 +02:00
parent 06cfd0d8ad
commit e3c73d9881
143 changed files with 5783 additions and 4051 deletions

View File

@@ -255,7 +255,7 @@ zap_client_common_handshake_t::zap_client_common_handshake_t (
mechanism_base_t (session_, options_),
zap_client_t (session_, peer_address_, options_),
state (waiting_for_hello),
zap_reply_ok_state (zap_reply_ok_state_)
_zap_reply_ok_state (zap_reply_ok_state_)
{
}
@@ -283,7 +283,7 @@ void zap_client_common_handshake_t::handle_zap_status_code ()
// i.e. 200, 300, 400 or 500
switch (status_code[0]) {
case '2':
state = zap_reply_ok_state;
state = _zap_reply_ok_state;
break;
case '3':
// a 300 error code (temporary failure)