What are the reasons for placing member functions in front of member variables or vice versa or vice versa?

Question

Given a class, what reasoning exists for either of the following two styles of code?

Style A:
class Foo {
    private:
        doWork();

        int bar;
}

Style B:
class Foo {
    private:
        int bar;

        doWork();
}

For me it's a tie. I like Style A because member variables feel finer and therefore more general member functions will be displayed. However, I also like style B because the member variables seem to define in OOP style what the class represents.

Are there other things to consider when choosing between these two styles?

Answer 1

In C ++, for those who use a class to define in code, in a header file.

Java ( ) , , , JavaDoc. IDE B.

:

• ++ A, .
• Java B, .

Answer 2

, , . () - ( ).

B , ( , A). B ( , java, #, php...)

Answer 3

, B , A. , ( , Unreal Script, ), B .

, , . , -.

Answer 4

UML, , : , , .

, , .

Answer 5

A , , , , .

Answer 6

, A, , , - . , , .

class A {
    int bar;
public:
    doWork();
};

Answer 7

++, - A, API, . - :

class SomeClass
{
public:
    void foo();
    void bar(int i);

private:
    int m_i;
};

, . - , , , , ().

, , () struct , , . - :

struct SomeMessage
{
    uint64_t m_id;
    int32_t  m_number;
    char     m_name[16];

    explicit SomeMessage(uint64_t id);
};

, - , . , , .