The mysqld handler part of NDB
ha_ndbcluster_binlog.cc, etc.) uses the same
coding style as the rest of the mysqld code.
The non-mysqld part of NDB code has a long history, and use a multitude of coding styles. When modifying and extending existing source files or modules, the coding style already used in that code should be followed in terms of indentations, naming conventions, etc. For completely new code, the mysqld conventions (with exceptions below) should probably be followed.
Do not do any change to NDB code purely for the sake of changing from one formatting style to another. It just causes merge annoyances and makes patches harder to read, and we do not expect the style to ever become 100% consistent across all of the source code. It is however ok to fix inconsistent style in lines that are changed for other reasons.
One convention that should be followed for all new or modified
code, in both mysqld and non-mysqld parts of the code, is that
class member variables should be named with lowercase words
separated by underscores
'_', and pre-fixed
'm_'. Like this:
const char *m_my_class_member;
Copyright © 1997, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices