don't allow wrong framework to be used
Don't add a duplicate copy of libtightdb-ios.a to the framework

I'm not entirely clear on how, but libRealm-fat.a already has a copy of
tightdb, so adding a second copy with libtool is unnecessary and makes the
final framework 25% larger.
Improve the error message when properties are of an invalid type

Try to make it clearer what the problem is, list the legal types for
properties, and add the relevant documentation URL.
Merge pull request #723 from realm/tg-duplicate-object-files

Don't add a duplicate copy of libtightdb-ios.a to the framework
Merge branch 'master' into al-platform
enforce correct framework for xcode6proj
use TARGET_IPHONE for everything
Merge pull request #721 from realm/al-platform

Don't allow framework for the wrong platform to be used
Merge pull request #724 from realm/tg-bad-property-type-error-message

Improve the error message when properties are of an invalid type
Fix memory leak when breaking out of a for-in loop

Use an autoreleased NSMutableArray to keep the temporary objects alive rather
than a heap-allocated id[] so that the last block of objects will get
autoreleased if the iteration does not complete. This results in iteration
breaking if the user drains the autorelease pool while iterating over the
RLMArray, but that's no longer supported with ARC and was always a bad idea.
Switch RLMArrayLinkView's fast enumeration implementation to RLMArrayTableView's design

The previous implementation autoreleased the objects being looped over,
resulting in them staying alive unpleasantly long.
Update changelog
Verify that objects are released during fast enumeration and not just at the end