Lint detects not initialized variables

We recently came across several problems we were not able to reproduce. One of them involved a pane that was not drawn ( no title, no content ).

The other involded a non-customizable/non-closable toolbar that disapeared forever.

And another that caused command bars to display under the panes.

 

Since we were not able to reproduce the problems, we scanned xtreme code using pc-lint. There were several cases where member variables were not initialized by constructor. This does not mean that they are not initialized at all, but it may be a clue that depending on the execution order, some members could be used before initialization.

 

If you are interested, I can send you the output of our scan.

 

Thank you,

Jansim

 

You must be aware that pc-lint is not 100% reliable. Sometimes it complains about uninitialized variables that are in fact initialized later, but "could" be uninitialized if the program was not executed in the expected order.

 

Well, it's up to you own judgement.

 

Thank you,

Jansim