Re: sup****ting header-less blocks in memory allocators...

"Chris M. Thomasson" <no@[EMAIL PROTECTED]
> wrote in message 
news:Me9Fk.39675$hX5.13116@[EMAIL PROTECTED]
> "Dmitriy V'jukov" <dvyukov@[EMAIL PROTECTED]
> wrote in message 
>
news:c1a7e985-758d-460b-9e16-eb4d4b40b0d9@[EMAIL PROTECTED]
> On Oct 2, 11:20 pm, "Chris M. Thomasson" <n...@[EMAIL PROTECTED]
> wrote:
>
>> > b = new buf<1234>[5];
>> > Humm... AFAICT, this is pretty neat for a C guy to look at!
>
>
>> Don't miss caveat I describe here:
>>
http://groups.google.com/group/comp.programming.threads/msg/1463529870b08125?hl=en
>
> What about:
>
>
http://groups.google.com/group/comp.programming.threads/msg/11a98f6836d38880
>
> Is that undefined behavior?

OOOOOHHHHH!!!



It works perfectly fine upon array delete... However, NOT on single object

delete!!!!! WTF!!!! Here is exact output:


custom_allocator::allocate(00246C50, 2234)
custom_allocator::deallocate(00246C50, 1234)
custom_allocator::allocate(00247760, 11174)
custom_allocator::deallocate(00247760, 11174)




What the ****%!!!!! I see, I am using sizeof(T)... ****%.