On 5/10/06, Shachar Shemesh <[EMAIL PROTECTED]> wrote:
The reason I was doing this was that a structure defined inside another class had a constructor that zeroed out the "Display" member. The function that initialized the display member was run by the initialization of another member of the same class, resulting in the display argument being overwritten by the relevant constructor.
The solution - reverse the order of the member definitions.
..
Yes, I know, it's my fault for using C++. The problem is that the
No, it's your fault for being dependend on member initialization order, you should get rid of this dependency before this bug will come around to get you again. I think "Effective C++" talks about this. (http://www.aristeia.com/books_frames.html) As for the avoidence of #ifdefs - an excellent argument, IMO. --Amos -- "(God) is my favourite fictional character." - Homer Simpson ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
