• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Might not respond to selector, an error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Might not respond to selector, an error


  • Subject: Might not respond to selector, an error
  • From: "Theodore H. Smith" <email@hidden>
  • Date: Fri, 15 Jul 2005 11:06:40 +0100

Hi people,

Is it possible to make ObjC warnings of "might not respond to this selector", an actual hard error?

I'd like to do this, because I like to press "Build and Debug" to build and debug my app, as it's more convenient. However, Xcode will actually debug an app which has warnings. This is fine, because some warnings are a pain to remove even if the code is good.

However, this does not catch "missing selector" warnings, which I think are serious enough to warrant not allowing the compiler to complete compiling.


--
http://elfdata.com/plugin/ Industrial strength string processing, made easy.


"All things are logical. Putting free-will in the slot for premises in
a logical system, makes all of life both understandable, and free."

_______________________________________________
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


  • Follow-Ups:
    • Re: Might not respond to selector, an error
      • From: "Sean McBride" <email@hidden>
  • Prev by Date: Re: Testing a framework using SenTestingKit and the debugger
  • Next by Date: Linking statically when a dylib exists
  • Previous by thread: Re: using gcc_select to switch to 3.x
  • Next by thread: Re: Might not respond to selector, an error
  • Index(es):
    • Date
    • Thread