I am running LPSI C + + MFC software in DevPartner Studio and complain about these lines a lot: Where PARAFORMAT is a class, any section has been started in this way, DevPartner pops this error: looks correct to me, which overrides the correct variable. Is this building right? Can I safely ignore the warning? Edit: Here's the paragraph file Without seeing PARAFORMAT, I have to take what happens. PARAFORMAT is a POD structure / square with the size of 156 bytes. For initializing all the members of the class, your initial syntax compels the compiler to generate the codec. Therefore, the compiler sets the initial 0, which you have specified in the initial list, and then clever and each other member variables individually. Instead of setting, the rest of the structure is set to 0. This is captured by a check in the Messepet call, DevPartner - it does not like you to call your local variable without a memset, and generate a warning. This is a broken probe in Devpartner, which you can ignore I reserve the right to change my mind / when you provide us with the rest of the information :) Edit: After looking at the PARAFORMAT structure, I believe the above description is correct PARAFORMAT pf = {0};
write overrun: memory Write 0x002B9D18 (152) local variable PF 0x002B9D14 (156) function in CServerWnd :: OnInitDialog; To make a call, in the parameter 1, the mametet
typedef struct _paraformat {UINT cbSize; DWORD dwMask; WORD wNumbering; Word break; Long dxStartIndent; Long dxRightIndent; Long dxoffet; Word wAignign; Small CTBcount; Long RGXTab [MAX_TAB_STOPS]; } PARAFORMAT;
Comments
Post a Comment