-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix ISO C naming violations of function names and header guards #21
Conversation
libvalkeycluster/tests/test_utils.h
Outdated
@@ -1,5 +1,5 @@ | |||
#ifndef __TEST_UTILS_H__ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why add VALKEY to each of these? Do you think there's a risk of macro name collission?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably no collision in src/, I mostly followed how its done in the non-cluster headers.
src/async_private.h: #ifndef VALKEY_ASYNC_PRIVATE_H
src/fmacros.h: #ifndef VALKEY_FMACRO_H
One (only?) benefit I can think of is that its already correct if we need to make a header public.
Signed-off-by: Björn Svensson <[email protected]>
Signed-off-by: Björn Svensson <[email protected]>
Signed-off-by: Björn Svensson <[email protected]>
Signed-off-by: Björn Svensson <[email protected]>
Signed-off-by: Björn Svensson <[email protected]>
Signed-off-by: Björn Svensson <[email protected]>
Signed-off-by: Björn Svensson <[email protected]>
…ey-io#21) * Update header guards after move of header files * Fix ISO-C naming violation by renaming internal functions: * ..SetError() * _valkeyClusterConnect() * __valkeyClusterAppendCommand() * __valkeyClusterGetReplyFromNode() * Remove internal func __valkeyClusterGetReply() * Remove internal func _valkeyClusterConnect2() Signed-off-by: Björn Svensson <[email protected]>
Closes #19