dev-cpp-users

Re: [Dev-C++] scope resolution +1

[Daniel G. <sp...@ho...>]

Thanks, I'll check those links later. That cleared that up, cheers.

Thanks to everyone who's been helping me out,
Daniel


>From: Jason Silverman <mys...@op...>
>To: dev...@li...
>Subject: Re: [Dev-C++] scope resolution +1
>Date: Fri, 19 Apr 2002 04:21:21 -0400
>
>It's an initalizer list.  A short summary of them can be found here,
>http://pstonge.stmarys.medford.or.us/adv_cpp_1/lectures/advanced_functions2.
>htm, and here, http://oakroadsystems.com/codeprac/inher.htm.  They're 
>short,
>but to the point.  Basically it's initalizing a data member to a value as
>it's created, instead of normal constructors which do so afterwards.
>
>Jason
>----- Original Message -----
>From: "Daniel Glenfield" <sp...@ho...>
>To: <dev...@li...>
>Sent: Friday, April 19, 2002 4:01 AM
>Subject: [Dev-C++] scope resolution +1
>
>
> > What does it mean when you have the scope resolution operator and the
>single
> > : in the same bit of code?
> >
> > e.g.
> >
> > CDialog1::CDialog1(CWnd* pParent /*=NULL*/)
> > : CDialog(CDialog1::IDD, pParent)
> >
> > ?
>
>
>_______________________________________________
>Dev-cpp-users mailing list
>Dev...@li...
>https://lists.sourceforge.net/lists/listinfo/dev-cpp-users


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.

RE: [Dev-C++] scope resolution +1

[Graeme F. <gr...@dr...>]

The CDialog1::CDialog1(CWnd* pParent /*=NULL*/) is the constructor for the
CDialog1 class. Now because this class will inherit from the CDialog class
it must be able to call the default constructor for the CDialog class.
However this class probably doesn't have a default constructor, in which
case the constructor has to be called explicitly, hence the line :
CDialog(CDialog1::IDD, pParent) which calls the CDialog constructor passing
it IDD a static variable from CDialog and pParent argument passed in. Now
that the CDialog constructor has been called the rest of the CDialog1
constructor can be executed.


>>What does it mean when you have the scope resolution operator and the
single
>>: in the same bit of code?
>>
>>e.g.
>>
>>CDialog1::CDialog1(CWnd* pParent /*=NULL*/)
>>	: CDialog(CDialog1::IDD, pParent)
>>
>>?

Re: [Dev-C++] Global variables (linking errors)

[Graeme F. <gr...@dr...>]

On a slightly different tack, it is often desirable to have a header file
included multiple times. However that may cause problems if you end up with
multiple definitions. To avoid that header guards should be used. These will
have a pre-processor directive around the entire file

#ifndef __MyHeaderFile_H
#define __MyHeaderFile_H

// add some declarations and definitions here...

#endif

This will expand the code only once but allow the file to be included
multiple times. Now all you have to be wary of is circular #includes, where
file A includes B and B includes A. That causes the compiler to get terribly
frustrated.

Graeme.