Support for Xcode6-Beta6 (Realm-Xcode6 and RealmSwiftExamples)
updated build.sh to use Xcode6-Beta6
changed instances of Xcode 6 Beta 5 to Beta 6
Merge branch 'master' into jp-xcode6-beta6

* master:
  Revert "Updating to XCode 6 beta 6"
  Updating to XCode 6 beta 6
  add test for notifications in bg threads
  changelog
  changelog
  api cleanup
  Don't claim that autorefresh is off by default on background threads
  use const for non-versioned version number
  fix for reusing cached objectSchema tables
  fix for async test conditions
  cleanup table creation flow, use only 1 transaction during migrations
  fix for swift tests
  only initialize the schema for the first thread accessing a realm at a particular path
Merge branch 'master' into jp-xcode6-beta6

* master: (62 commits)
  Update docs + installation instructions
  initWithContentsOfURL ends up on the wrong thread.
  Links are no longer blue, and do change color when selected
  Change how Realm in linked into TestHost
  improved wording
  Minor docfix: mentioning that array has to be in right order
  Lock button locks everything
  Column fitting faster, minor cleanups
  Saves window size and to some extent position (seems to be some automatic cocoa behaviour that influences this) between session.
  Throw an exception if the user asks for case-insensive matching on link queries
  Add better string comparison query tests
  Eliminate some weirdness in add_constraint_to_query
  Removed spacing in front of class names
  Fix some issues with multilevel link queries
  Eliminate more of the differences between link and regular queries
  Enable unused parameter warning in the Xcode 6 project
  Extract some duplicated query building logic and add support for multi-level link queries
  Extract some duplicate code for ORing queries
  Add a helper for checking predicate preconditions
  Implement the IN operator for link queries
  ...
Merge branch 'master' into jp-xcode6-beta6

* master:
  Improve the migration documentation more
  Fix some typos
  Improve the migration documentation
  Fix a bunch of small errors in the RLMRealm docs
  Improve the autorefresh documentation
  Don't set TIGHTDB_MAX_LIST_SIZE for debug builds
  Upgrade core library version 0.82.0 -> 0.82.1
  Fix crash when adding an object already in a realm to another realm
  Update changelog
  Updates necessitated by change core Group API (https://github.com/Tightdb/tightdb/pull/515)
  Upgrade core library version 0.81.0 -> 0.82.0
  Use an exception rather than assertion
  Check the token's block in case it was niled while being enumerated
  Make sure the token block is not nil

Conflicts:
	CHANGELOG.md
Merge branch 'master' into jp-xcode6-beta6

* master:
  Actually report failure from build.sh when a test fails
  Update README.md
  Update README.md
  Update README.md
  License details; let us know about your apps!
Merge branch 'master' into jp-xcode6-beta6

* master:
  disable failing test in XCode6
  Add better tests for querying RLMArrays from queries
  explicit query copy
  changelog
  added test, fix for re-sorting
  fix for enumerator test
  enum cleanup
  make sure new tableview is attached
  create tableview on demand
  Upgrade core library version 0.82.1 -> 0.82.2
  Document RLMRealm lifetimes and related issues
  small modifications from PR feedbacl
  updated CONTRIBUTING.md with guides to filing issues and contributing code
Bump version number
Merge pull request #814 from realm/jp-xcode6-beta6

Support for Xcode6-Beta6 (Realm-Xcode6 and RealmSwiftExamples)
Use std::unique_ptr to hold pointers to C++ types

Cuts down on cleanup code and fixes a memory leak when creating a shared
group throws an exception.
Implement read-only realms

No docs changes because the implementation matches what the docs previously
claimed.

Some assorted design decisions made in the process:

1. refresh and addNotificationBlock are considered "mutating" methods and
disallowed on read-only realms on the grounds that they make no sense.

2. RLMRealm is split into RLMMutableRealm and RLMReadOnlyRealm. This is purely
an implementation detail to slightly simplify the implementation and slightly
improve performance (no checks for the readOnly property). It could be
beneficial to expose this separation in the interface as they do have different
APIs, but I didn't really feel it was worth it.

3. Missing tables in read-only realms are simply treated as if they were empty.
I wanted to make extra columns in tables or missing columns with default values
treated similarly (so that you'd be able to open any realm file that either
matches the schema or can be auto-migrated to the schema), but that'd require
creating separate accessor classes and is far more complexity than it's worth.

4. No attempt is made at handling the case of a read-only RLMRealm in one
process and a mutable RLMRealm in another process sharing a realm file. There's
no easy solution, and more complex solutions (like putting a lock file in /tmp)
should be done in the core and are not very high priority.

5. Realm files must already exist to be openable in read-only mode. Treating a
nonexistent realm as an empty realm is theoretically doable, but would be
awkward (and kinda dumb).
Refactor the implementation a bit

Eliminate the Mutable/ReadOnly subclasses and clean up all the objectstore
stuff.