void pointers

Fucking void pointers, how do they work

is it possible to deallocate a pointer casted void to an array consisting of anything besides primitive types, aka objects allocated on the heap?

ex:
Obj *array = new Obj[5];
void *cocks = (void *) array;

free(cocks);
or
Array *morecocks = (Array*)cocks;
delete [] morecocks;

on the same note, what is wrong with this code, dont say bad style i'll fucking kill you, that's not the point of it
dumbed down version:

size_t Size = 2;
Balls<int> *atest = new Balls<int>[Size];
void *vtest = (void *)atest;
ASS( vtest, sizeof(Balls<int>), Size, 5 );
delete [] atest;
atest = (Balls<int> *)vtest;

ASS does a manual realloc and index copy with last arg as new size (tested), and Balls has an <int> array and some other member variables

    for( int counter = 0; counter < 2*sizeof(Balls<int>); ++counter )
        std::cout << int(((char*)((void*)atest))[counter]) << ' ';
 returns the same values before and after (on the stack), but any atest.array[anything] now returns garbage

How juvenile.

code has terrible style

If you're not malloc-ing it, don't free it. In fact, don't malloc ever, because you're using Sepples and shit could confuse you if you're using more than one method of memory management.

No matter what your compiler does, the standard says that, while you can cast any pointer (not function pointer) to a void pointer, you can not do anything with it except cast it back to a pointer of the original type.

>>5
Only if you want it to still mean anything.

>>6
Shut up.

>>7
Hax my anus.

>>5
Fuck your shit.

-fno-strict-aliasing

>>9
That's not what that does.

>>10
Prove it.

>>11
Disprove it.

>>12
I asked first.

What's with the C/C++ related threads as of late? Wasn't this a Lisp board?

>>14
C/C++
IHBT

>>15
He meant C++/Java.

DON'T REPLY