Re: Turning off 'deleting 'VOID*' is undefined' error
Re: Turning off 'deleting 'VOID*' is undefined' error
- Subject: Re: Turning off 'deleting 'VOID*' is undefined' error
- From: Laurence Harris <email@hidden>
- Date: Mon, 29 Jan 2007 04:58:19 -0500
On Jan 29, 2007, at 1:56 AM, Mike wrote:
Porting a bunch of Windows C++ (which I didn't write) to Xcode.
Apparently a void* is being used as a field of a struct which holds
a ptr to an object and the actual object type (class) can vary.
I believe the "right" way is to use a pointer to a base class that
all the possible objects share. What you have currently is the kind
of thing that requires lies to the compiler and prevents C++ from
doing things it was designed to do for you.
Larry
Mike
Chris Espinosa wrote:
On Jan 28, 2007, at 7:25 PM, Mike wrote:
Is there a setting in Xcode 2.4.1 for turning off the
warning: deleting 'VOID*' is undefined
warning?
No, there isn't. The C++ standard says you can only delete()
things allocated with new(), as delete() must call free() first.
So the compiler cannot generate correct code for delete of a 'void
*'. The warning is there to warn you that your code may be doing
any number of unintended things.
What are you really trying to do?
Chris
_______________________________________________ Do not post admin
requests to the list. They will be ignored. Xcode-users mailing
list (email@hidden) Help/Unsubscribe/Update your
email@hidden This email sent to lists@michael-
amorose.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden