C / C++ / MFC

static uint32_t usb_error = 0;   // is (global) static initialized to 0 as default anyway? 

usb_task_state = USB_DETACHED_SUBSTATE_INITIALIZE; // why "initialized " again here? 

bmHubPre     = 0;            // is this necessary? see constructor parameter 

ASSERT(usb_task_state == USB_DETACHED_SUBSTATE_INITIALIZE);

// Header file
class USBHost
{
    // ...
protected:
    static uint32_t usb_error;
    static uint32_t usb_task_state;
}

// Source file
uint32_t USBHost::usb_error = 0;
uint32_t USBHost::usb_task_state = USB_DETACHED_SUBSTATE_INITIALIZE;

usb_task_state = USB_DETACHED_SUBSTATE_INITIALIZE; // why "initialized " again here? 

Quote:

static uint32_t usb_error = 0; // is (global) static initialized to 0 as default anyway?

static uint32_t usb_error = 0;   // is (global) static initialized to 0 as default anyway? 
static uint32_t usb_task_state = USB_DETACHED_SUBSTATE_INITIALIZE; // this state is not defined as 0 - this is OK  

USBHost::USBHost() : bmHubPre(0) // may be a default USB hub 0 , not sure 
{
     usb_task_state = USB_DETACHED_SUBSTATE_INITIALIZE; // why "initialized " again here? 
 
     init();
}

void USBHost::init()
{
     devConfigIndex     = 0;            // USB (device ?) default index
     bmHubPre     = 0;            // is this necessary? see constructor parameter
}

Vaclav_Sal wrote:

I sure wish there was an easier way to "see" the objects hierarchy in Arduino code.

Quote:

The compiler may or may not initialize for you, but why risk it.

CPallini wrote:

The C++ standard specify that such variables 'shall be zero-initialized'

Albert Holguin wrote:

Was this in every C++ standard since the original? ...I don't really know...

Albert Holguin wrote:

it's not worth any savings in writing. Plus it makes it easier to read.

class Shape { virtual void Draw() = 0; /* ... */ };
class Circle : public Shape { void Draw(); };

class Canvas {
public:  void Draw();
private: set<Shape*> m_shapes;
};