Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: "Will be initialized after": does it matter?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Will be initialized after": does it matter?

Subject: Re: "Will be initialized after": does it matter?
From: Patrick Coskren <email@hidden>
Date: Tue, 12 Dec 2006 16:47:23 -0500

On Dec 12, 2006, at 4:39 PM, Mark Wagner wrote:

I'm getting the following warning when compiling my project:

MBOOK.H: In constructor 'MBook::MBook(id, tag, id)':
MBOOK.H:201: warning: 'MBook::ostrQuestionTypeHeaderVOD' will be
initialized after
MBOOK.H:190: warning:   'MString MBook::oAbbrev'
MBOOK.CPP:112: warning:   when initialized here

What does it mean, and does it matter?

Without seeing the code, this is just a guess... make sure ostrQuestionTypeHeaderVOD and oAbbrev are declared and initialized in the same order. My language manual's at home, so I can't recall the exact reason, but there are cases that can be ambiguous if you don't use the same order both times, and that's what it's making sure you're aware of.

-Patrick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: "Will be initialized after": does it matter?
From: Scott Ribe <email@hidden>


References:  
  >"Will be initialized after": does it matter? (From: "Mark Wagner" <email@hidden>)




Prev by Date:
"Will be initialized after": does it matter?

Next by Date:
Re: "Will be initialized after": does it matter?

Previous by thread:
"Will be initialized after": does it matter?

Next by thread:
Re: "Will be initialized after": does it matter?

Index(es):

Date
Thread