https://smaugmuds.afkmods.com/index.php?a=rssfeed&t=1121 The largest Smaug community resource site. - en SmaugMuds 60 https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15875#p15875 You're right, I should have made it more clear that when I said 'member object', the word 'object' was very deliberately chosen. :wink: That said, some container types over primitives like int etc. will call the constructor (initializer might be a more appropriate term) when they find that they need to insert objects, e.g. to fill up space in a vector if you inserted past the last element. But that's different from new's behavior. https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15875#p15875 Fri, 5 Sep 2008 10:48:20 CDT Coding nobody@example.com (David Haley) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15874#p15874 It'll call constructors for any non-POD type, but it won't do it for basic types. So your ints and so on will still be uninitialised. https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15874#p15874 Fri, 5 Sep 2008 05:54:34 CDT Coding nobody@example.com (Kylotan) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15406#p15406 Well, actually, when you call 'new', it also calls the constructor of every member object of the object. For instance, if you have a struct that contains string objects, creating one with 'new' will initialize those string objects correctly. That is the default behavior. Note that this does not apply to pointers. As a minor correction to my remark from a few months ago, the constructor is also called if you create something on the stack, e.g. for: string s; string*s = new string(); bot https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15406#p15406 Mon, 23 Jun 2008 10:54:11 CDT Coding nobody@example.com (David Haley) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15403#p15403 [quote=Samson] From "man calloc": [quote]calloc() allocates memory for an array of nmemb elements of size bytes each and returns a pointer to the allo-cated memory. The memory is set to zero. If nmemb or size is 0, then calloc() returns either NULL, or a unique pointer value that can later be successfully passed to free(). malloc() allocates size bytes and returns a pointer to the allocated memory. The memory is not cleared. If size is 0, then malloc() returns either NULL, or https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15403#p15403 Sun, 22 Jun 2008 14:23:57 CDT Coding nobody@example.com (Noplex) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15402#p15402 Ooo, double thread necromancy! That's gotta be worth some extra points or something :P From "man calloc": [quote]calloc() allocates memory for an array of nmemb elements of size bytes each and returns a pointer to the allo-cated memory. The memory is set to zero. If nmemb or size is 0, then calloc() returns either NULL, or a unique pointer value that can later be successfully passed to free(). malloc() allocates size bytes and returns a pointer to the allocated memory. The me https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15402#p15402 Sun, 22 Jun 2008 13:57:34 CDT Coding nobody@example.com (Samson) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15401#p15401 [quote=DavidHaley]You need to initialize it with 'new' if you want the constructor to be called.[/quote] If you need a pointer you need to initialize it with new. The default constructor (if one exists) will be called as long as you don't allocate a block of memory with malloc. A constructor will also be called, if one exists, if an assignment operation is used and there is no explicit keyword before the constructor. Examples: [code] class foo { public: foo(void) { std::cout << "de https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=15401#p15401 Sun, 22 Jun 2008 12:22:59 CDT Coding nobody@example.com (Noplex) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=13593#p13593 It's perfectly fine to have constructors in structs. A class is nothing more than a struct with visibility modifiers. The problem is that if you initialize an object with malloc, the constructor is not called. You need to initialize it with 'new' if you want the constructor to be called. (Similarly for destroying it with free vs. delete.) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=13593#p13593 Mon, 10 Dec 2007 01:06:04 CST Coding nobody@example.com (David Haley) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=13588#p13588 Heh. The joy of old posts. At some point I figured out what was wrong with this since the test command loads and outputs what I was expecting it to. It's too bad the rest of my code is in such disarray at the moment or I might be able to remember why I was doing this to begin with. https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=13588#p13588 Sat, 8 Dec 2007 22:26:15 CST Coding nobody@example.com (Samson) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=13587#p13587 [quote=Samson][code] struct weapontable { weapontable(); char *flags; /* Default flag set */ char *name; /* Descriptive name */ float weight; /* Base weight */ float cost; /* Base cost/value */ short type; /* Weapon type */ short wd; /* Base damage */ short skill; /* Skill type */ short damage; /* Damage type */ }; vector<weapontable*> w_table; weapontable::weapontable() { init_memory( &flags, &damage, sizeof( damage ) ); } [/code https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=13587#p13587 Sat, 8 Dec 2007 18:26:17 CST Coding nobody@example.com (Quixadhal) https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=4103#p4103 Don't know why I didn't try this before, but I threw the code up on Cygwin and had at it. Since it uses older gcc 3.4.4, I figured it might ferret out a potential compiler problem. Well, that's exactly what this turned out to be. Without altering a single line of code, Cygwin compiled it and ran it without crashing. Which is why I was stumped. Perfectly valid code crashing out for no explainable reason. I'd file a bug against the compiler for this, but I wouldn't know where to begin. Isolatin https://smaugmuds.afkmods.com/topic/a-nice-fat-stumper-for-you-all-1121/&p=4103#p4103 Mon, 20 Mar 2006 08:48:31 CST Coding nobody@example.com (Samson)