tag:blogger.com,1999:blog-19599775.post2495542538916240193..comments2022-03-02T22:38:18.781+01:00Comments on Cristian Adam's: Reusing bitsCristianhttp://www.blogger.com/profile/16735332457747999220noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-19599775.post-35962842590902856022011-05-31T11:57:17.118+02:002011-05-31T11:57:17.118+02:00sure it's the same as reinterpret_cast, but yo...sure it's the same as reinterpret_cast, but you have the benefit of confusing everyone who reads the code ;)raduhttps://www.blogger.com/profile/08271427533328060790noreply@blogger.comtag:blogger.com,1999:blog-19599775.post-9992165214224848332011-02-10T06:47:25.999+01:002011-02-10T06:47:25.999+01:00If you write a new memory allocator in C++ you def...If you write a new memory allocator in C++ you definitely use the placement new. I used around here: https://code.google.com/p/heavy-malloc/ - I think you can find other examples too :)<br />Neat trick, but it's actually the same thing as a cast/reinterpret_cast :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-19599775.post-36997726038244893582011-02-10T00:15:23.539+01:002011-02-10T00:15:23.539+01:00I think ATL collection classes are doing this in o...I think ATL collection classes are doing this in order to instantiate an element on already existing/allocated memory block.Anonymousnoreply@blogger.com