C / C++ / MFC

Jochen Arndt wrote:

pFoo is a value of type int*

void PassByPointer(int* pFoo)
{
    *pFoo += 1;  // manipulates whatever pFoo points to
}

void PassByReference(int& rFoo)
{
    rFoo += 1;  // manipulates whatever rFoo refers (i.e. points) to
}

int PassByeReference(B& Parameter)

 #include <stdio.h>

void f(int &x) { x += 1; }

int main(void)
{
    int n = 1;
    printf("n = %d\n", n);
    f(n);
    printf("n = %d\n", n);

    return 0;
}

Member 868926 wrote:

when a header is clicked:

void MyClass::OnLvnColumnclickList(NMHDR *pNMHDR, LRESULT *pResult)
{
    LPNMLISTVIEW pNMLV = reinterpret_cast<LPNMLISTVIEW>(pNMHDR);
 
    mCSVListCtrl.DeleteColumn(pNMLV->iSubItem);// This IS getting zero
 
    *pResult = 0;
}

Any ideas?

mCSVListCtrl.DeleteColumn(0);

Victor Nijegorodov wrote:

Just for a test: what will happen if you call

mCSVListCtrl.DeleteColumn(0);

from anywhere but from this MyClass::OnLvnColumnclickList(...) message handler?

Member 868926 wrote:

Any ideas?

AfxCheckMemory[^]

This function works only in the Debug version of MFC.

Quote:

I am quite sure the reason I got an assertion was because I did a SetDlgItemText without some how creating a m_hWnd

ForNow wrote:

On more thing should assert only be used in "debug"

assert Macro, _assert, _wassert[^]

The assert macro is enabled in both the release and debug versions of the C run-time libraries when NDEBUG is not defined. When NDEBUG is defined, the macro is available but does not evaluate its argument and has no effect. When it is enabled, the assert macro calls _wassert for its implementation. Other assertion macros, _ASSERT, _ASSERTE and _ASSERT_EXPR, are also available, but they only evaluate the expressions passed to them when the _DEBUG macro has been defined and when they are in code linked with the debug version of the C run-time libraries.