3 ms·
>Except this isn't forcing good behavior, it is forcing being explicit. Go ahead and use `!` it will work like you are used to. That's not correct. `!` will c
by mpweiher 12y ago
>Except this isn't forcing good behavior, it is forcing being explicit. Go ahead and use `!` it will work like you are used to.
That's not correct. `!` will crash without recourse where ObjC simply ignores the message and Java raises a catchable NPE.
- Guvante 12y agoIf you actually do a null check all of the languages work the same. Since in all but the prototype cases you will be doing a null check does it really matter? > ObjC simply ignores the message Don't quote this like a benefit please, it is a horrendous design. > Java raises a catchable NPE Only difference between this and a crash is in theory you can log. In the majority of cases a NPE is bringing you down anyway.
- mpweiher 12y ago>> ObjC simply ignores the message >Don't quote this like a benefit please, it is a horrendous design. Hmm..so the ? operator for optionals should removed from Swift?