New AppCode 3.4 EAP, build 145.184

Stanislav Dombrovsky

Hi everyone,

New AppCode 3.4 EAP, build 145.184 is available for download. The patch update is also available if you are using previous 3.4 EAP build.

This build addresses the following important issues:

  • Incorrect intentions about missing localization (OC-6896)
  • Problem with Rename refactoring for already localized strings (OC-11707)
  • Slow autocompletion appeared since build 144.4199 (IDEA-151684)

From the C++ side this build delivers a lot of changes in Quick documentation. In addition to the information that is already displayed, AppCode will show hyperlinks for types referenced in documentation (works now for classes, structs, unions and enums) and the following declaration modifiers that were omitted before:

  • function specifiers (inline, virtual, explicit, final)
  • constexpr specifier (constexpr)
  • storage class specifiers (register, static, thread_local, extern, mutable)
  • cv qualifier (const, volatile, mutable)
  • typedef
  • typename

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

Comments below can no longer be edited.

5 Responses to New AppCode 3.4 EAP, build 145.184

  1. ali kiran says:

    March 6, 2016

    how long will it take for proper support to swift, there is still appcode not comfortable for smooth development and lack of latest swift features like a new selector syntax.At least we need xcode like autocompletion and suggestion to fields.thanks for effort anyway

    • Pat says:

      March 7, 2016

      It’s nothing but hubris from JetBrains that they have stuck to writing their own parser for Swift. If they have legitimate reasons for using their own parser, then they should have used SourceKit as an interim solution and then worked on their own parser in parallel, switching over only when their own parser becomes stable. It’s very dissatisfying that, as paying customers, we’re effectively alpha testers for their half-baked parser.

      • Stanislav Dombrovsky says:

        March 7, 2016

        It’s very dissatisfying that, as paying customers, we’re effectively alpha testers for their half-baked parser.

        We are very sorry to make you feel that way and we will do our best to change it.

        If they have legitimate reasons for using their own parser, then they should have used SourceKit as an interim solution and then worked on their own parser in parallel, switching over only when their own parser becomes stable.

        Pat, we understand that it could be the best solution, and here I want to describe, why we did not use it for the moment. The first reason for it is that if we will try to use it as interim solution, it will require much more efforts from us rather than writing our own parser, because we will not be able to use the most of IntelliJ platform features and we will need to write it from scratch. So, we will spent our efforts, re-write the entire language model and after it we will still need to implement everything again, because we will not be able to implement the most of smart features. If we will implement Swift support according to our language model, as soon as we’ll finish it, we will be able to implement any smart feature much faster.

        The second reason is that when we started to work on the Swift support, SourceKit was not open-sourced and we just could not use it.

        May be we will use it for some features in the future, but our current understanding is that it will not allow us to work faster.

        • Chris Hatton says:

          July 8, 2016

          Just want to say, while I miss using AppCode while waiting for full parsing, I also support your position and have complete faith in JetBrains Devs to write the best Parser 🙂

          Best of luck, patiently looking forward to it.

    • Stanislav Dombrovsky says:

      March 7, 2016

      Usually it takes some time to support language changes. New selector syntax appeared in Xcode 7.3 beta 4 (as I remember, it was released 2 weeks ago), so as soon as we will have available resources – we will implement these changes.

Subscribe

Subscribe to product updates