🚀 go-pugleaf

"fwang11" <fwang11@pub3.fz.fj.cn> writes:

>>Which class would you propose to embed it in?  
>
> could embed it in another class, eg  
>
> class TForm1: public TForm
> {
>       private: 
>         TForm2 *Form2; 
> }

That's fine and all, but you still have to have an instance of TForm1
before you can access the pointer to Form2.  If Form2 really depends
on having a Form1 already made, then write your code exactly like you
have it above, and take form2 out of the auto-creation list.

>>Does it really matter?
>
> To make it pure C++ instead of mix C and C++.

First, how is this C instead of C++?

Second, what is wrong with C (even if this were C?)

Third, why is this better?


Making Form2 be a member of Form1 is a fine design idea, and you're
free to do it.  But the auto-created forms (created by starting your
application, without any code by you needing to be written) are
implemented with a global variable.  If you move form2 into form1,
then you're changing the meaning of your program.  Before, form2 was
created by the generated code at program startup.  Your proposal makes
it that form2 isn't created until sometime after form1 is created, and
you have to write (by hand) the code to create the object and
initialize the Form2 pointer that is inside form1.

Both are valid designs that accomplish different things.


-- 
Chris (TeamB);