Reorder testing of selectors.

Pick off the selector natively handled first. NSProxy's base (on my
current OS atleast) will attempt to forward things, and the fact
that the LightWeight proxy then eats the forward where there is no
target objc seems to confuse things.

This all makes the unittests fail when run in release mode, so it
just generally seems safer to reorder this.

The footnote, is NSProxy really defines a class method for this, but
since LightweightProxy doesn't have a fixed class to check with, it
can't really provide that method.

0 files changed, 0 insertions, 0 deletions