Newbie Q - Pointer vs None pointer references.

Ok,
This has been bugging me for about a week now. It's sort of a C++ question but since it's in the context of MFC, I figured I'd drop it here.

Now I know the '->' operator is for referencing members and member functions of a class or struct referenced by a pointer. I know the '.' is used to reference members and member functions of a class or struct represented by an object as aposed to a pointer.

Now that may have been confusing but the code I have here should clear it up. The book I'm studying on MFC has described accessing the same types of objects in BOTH ways in differing pieces of code but never explains why he chose to access it in that way.

Code:

---

    CDialog dlg(IDD_ABOUTDIALOG, this);
    dlg.DoModal();

---

And now this way...

Code:

---

    CDialog* dlg = new CDialog(IDD_ABOUTDIALOG, this);
    dlg->DoModal();
    delete dlg;

---

Now I know in the second instance the dialog was created dynamically via the 'new' keyword, but what I don't understand is why he made dlg a pointer rather then an object? He's also done this with CPaintDC as well (not to mention CPen, CBrush and a few others) and I can't get a handle on the reason behind the variations.

Any help would sure be appreaciated.

P.S. C++ and MFC are both new to me (2 months now) Aside from the dumb question, does it sound like I'm getting a handle on this stuff or does it sound like I'm still completely lost?

Well, assuming you will be discarding the object referenced by the pointer, then that would be most advantageous. Barring that, I think it's simply a matter of preference...

Basically, anything you put on the freestack with the new operator is permanent until you delete it. This gives you the option of controling your own memory allocation. Concerning the dialog box there is a main difference in that when you do the DoModal(), the dialog box will stay with the focus until you release it. With the pointer, new and Create() you can change the focus off of the dialog box to another window.

When you use pointers with CBrush, CPEN, etc you can create it once and use these over and over by simply referencing the address(&) to the pointer. Secondly by doing this you will only be passing a 4bit pointer instead of an entire class or struct if you send it to a function. This is why you send pointers referencing class's like CPaintDC, CClientDC or just the CDC class instead of the entire class.

This probably has something to do with The modeless option of displaying Dialogs. If they're not created dynamically, they'll only appear for a second.. due to the variable going out of scope and destroying the object.

digital dropout,
The book did speak about the difference between creating them locally on the heap through the first method whereby it's supposed to destroy itself as soon as it goes out of scope, and creating it manually via the second method where you need to manually delete the object yourself.

You raised a good point regarding moving a pointer around rather then the entire class or struct. I hadn't thought of that one at all.

The bug up my butt with this author is the variation from code sample to code sample for no apparent reason. In the last sample he created the dialog as an object rather then a pointer only to use it for one dialog box.:confused:

Duel-Catfish,
I'm not sure what your refering to. I've not seen anything of the sort. But then again, everything I've been doing is Modal.

When you init dialogs with the Create() or create() member function (I can't remember) they're created modeless, meaning, you can switch back to your program and the dialog freely. With modal, you must dismiss the dialog and return a value to the program before you can switch back to the actual program. If you use create() on the stack, the variable will go out of scope as soon as the calling function exits, and your modeless dialog will be nothing more then a flicker on the screen.

Dual-Catfish,
OK, Now I get ya.. Something akin to setting dialog visibaility to false..:D except the modeless one is actually "outa there"