{"id":306,"date":"2006-08-28T14:31:19","date_gmt":"2006-08-28T14:31:19","guid":{"rendered":"http:\/\/www.icemark.com\/blog\/archives\/2006\/08\/28\/doomdarks-revenge-6\/"},"modified":"2011-03-08T01:08:42","modified_gmt":"2011-03-08T01:08:42","slug":"doomdarks-revenge-6","status":"publish","type":"post","link":"https:\/\/www.icemark.com\/blog\/archives\/2006\/08\/28\/doomdarks-revenge-6\/","title":{"rendered":"Doomdark’s Revenge"},"content":{"rendered":"

I sat down today to do some DDR code, first in a while, and spent 3 hours debugging some crashes!<\/p>\n

Don’t you just hate it when you leave your code in a none working state! One was some bad XML, incorrect closing elements, and the other was some memory being trashed. The memory problem was due to my string class doing a shallow copy on assignment… well actually it wasn’t, but the compiler was for some reason not using my string assignment operator and instead doing it itself! Actually I have no idea what the compiler is doing at that point… grr…
\n
\nIt seems that the compiler differentiates between these two bits of code…<\/p>\n

figure1
\n
\nint example_function ( const string& source )
\n{
\n string new_string = source ;
\n}
\n<\/code><\/p>\n

figure2
\n
\nint example_function ( const string& source )
\n{
\n string new_string ;<\/p>\n

new_string = source ;
\n}
\n<\/code><\/p>\n

figure2 creates the correct constructor code for new_string and the correct assignment operator call for new_string = source. Figure one just makes new_string exactly equal to source. I think I must be missing something somewhere!<\/p>\n\"Technorati\"\/<\/a> C++<\/a>, programming<\/a>, source<\/a>, string<\/a>, constructor<\/a>, operator<\/a>\n

Related Posts:<\/h3>