AppCode 2016.1.3 update is out

Hi,

AppCode 2016.1.3 update is available for download. If using AppCode 2016.1 or 2016.1.2b, you will get an automatic notification in the IDE.

Swift 2.2

This update delivers parsing, highlighting and completion for the following Swift constructs:

  • associatedtype keyword.
  • #file, #line, #column and #function debug identifiers:
    Debug identifiers
  • new typesafe #selector directive:
    Typesafe selector
  • Swift version build configuration option:
    Build version check
  • keywords used as argument labels:
    Keywords as argument labels
  • function naming with argument labels.

Besides, Swift string interpolation works much better in this update with quote parsing issues fixed.

Mixed code

This update brings correct resolution for classes from Swift frameworks added as a dependency to an Objective-C project and vice versa. Together these changes should significantly improve mixed code editing, by bringing more correct navigation and Rename refactoring for Swift classes used from Objective-C code, better completion and more accurate results for symbol usages search.

Structure View

Two new sorting modes are available in Structure View (⌘7) for Objective-C and C++: Sort by Type and Sort Alphabetically. Type sorting groups entities in the following order:

  • namespaces
  • structures
  • classes
  • constructors/destructors
  • functions
  • typedefs
  • global variables
  • #define directives

In case you select alphabetical sorting, elements in each of the group will be sorted, that makes sense for a long files with lots of entities in it.
Build version check
Both sorting options respect #pragma mark labels order and in case you have them in your source code, they will be displayed correctly.

Other fixes and improvements

Find complete release notes here and feel free to share your feedback in the comments section below.

Your AppCode team
JetBrains
The Drive to Develop

Comments below can no longer be edited.

3 Responses to AppCode 2016.1.3 update is out

  1. Wilfred says:

    June 2, 2016

    The code in that screenshot is actually bad (the #selector() name doesn’t match the func name). I’m eagerly awaiting the 2016.2 EAP that adds the syntax error highlighting… and it looks like you guys need this feature too! 🙂

    • Stanislav Dombrovsky says:

      June 2, 2016

      Thanks, fixed. Check out the 2016.2 EAP )

  2. Francis says:

    June 2, 2016

    I’m seeing a pretty big performance regression with this build, seems like doing anything causes my CPU to spike to around 100%

Subscribe

Subscribe to product updates