Imprecise boost exception because of wrong value type when loading (tmLanguage) plist

[sparr]

Attempting to load a tmLanguage file containing the following snippet:

    <dict>
        <key>comment</key>
        <string>end of line comment</string>
        <key>match</key>
        <false/>
        <key>name</key>
        <string>comment.line.number-signx</string>
    </dict>

results in this error:

Error loading syntax file "Packages/User/marbelous.tmLanguage": boost::bad_any_cast: failed conversion using boost::any_cast

[FichteFoll]

Note that this itself is not a bug, but that Sublime Text's error message should be clearer.

[FichteFoll]

There were improvements to this in 3068. You can now get the following error messages:

    <duct>
        <key>match</key>
        <string>//.*</string>
        <key>name</key>
        <string>comment.single.line.sublime-settings</string>
    </duct>

error parsing lexer: ...tmLanguage: Unrecognised plist element duct

    <array>
        <key>match</key>
        <string>//.*</string>
        <key>name</key>
        <string>comment.single.line.sublime-settings</string>
    </array>

error parsing lexer: ...tmLanguage: Unrecognised plist element key

    <dict>
        <key>match</key>
        <string>//.*</string>
        <key>name</key>
    </dict>

error: Error loading syntax file "...tmLanguage": Expected value

The example in OP yields the following error:

error: Error loading syntax file "...tmLanguage": Wrong type for key match expected string

---

All in all, the error messages are pretty workable, except that they don't show where the error occured and that "Unrecognised plist element key" is shown instead of "expected array" or "expected dict". I'll leave this issue open for that and reduce severity back to trivial.

[FichteFoll]

Color schemes could also use some love.

If I change a value from being a string to an integer I get the following:
error: Error loading colour scheme ...tmTheme: Unabled to open color scheme ...tmTheme: malformed plist