Re: -performSelector: exception... in one build configuration
Re: -performSelector: exception... in one build configuration
- Subject: Re: -performSelector: exception... in one build configuration
- From: Steve Christensen <email@hidden>
- Date: Fri, 04 Nov 2011 12:53:51 -0700
On Nov 4, 2011, at 9:57 AM, David Duncan wrote: On Nov 4, 2011, at 9:11 AM, Christiaan Hofman wrote: This should not work. It fails for me with an error saying "Initializer element is not a constant".
If the source file is Obj-C++ it would work (because C++ would arrange for it to do so).
Indeed my file is Obj-C++ (.mm). And when I look at each struct in the debugger, it correctly shows the field containing the selector and displays the selector's name next to its address.
I also looked at the disassembly of that source file, and the SEL fields all show a reference to a string literal in the executable's text section, which makes sense since it appears that SEL is currently just a pointer to a null-terminated C string.
But even in that case I don't know why it would fail...
Nor I. The only thing I can think of is if the message dispatcher is comparing selector addresses instead of values, and that for some reason this one case ended up with two copies of a SEL.
|
_______________________________________________
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