EZFormRadioField

[Noobish1]

Is there a reason why EZFormRadioField uses NSException's instead of NSAsserts?

[jessedc]

Asserts get compiled out in release builds, I'd assume @chrismiles wants the exceptions to stay there.

[Noobish1]

Xcode throws errors if the "Enable Objective-C Exceptions" is set to No, which seems to be the default for me in Xcode 4.5.2

EDIT: under further inspection, the default does seems to be Yes, so it's just our project.

[chrismiles]

Throwing exceptions to indicate invalid state was a clean way to inform the API user, at the time. I'm not married to them, happy to hear arguments about using assertions instead.

I haven't seen a project not have "Enable Objective-C Exceptions" enabled. Is that common?

[Noobish1]

I've never come across a project with "Enable Objective-C Exceptions" set to No either, until now. The project is a Unity project with some native code and it seems like Unity is turning it off, NSAsserts work whether it's turned off or not so it seems like a better solution, but thats just me.

[chrismiles]

If you can easily work with it as it is, I think we'll just leave it.

However, if this is a show-stopper for your project, shout and I'll consider the change.