Having Swift and Objective C in a same project

Mix and Match Overview:

Objective C and Swift files can coexist in a single project, whether the project was originally an Objective -C or Swift project. This natural workflow makes creating mixed-language app and framework targets as straight forward as creating an app or framework target written in a single language.

The process for working with mixed-language targets differs slightly depending on whether you're writing an app or a framework. The general import model for working with both languages within the same target is depicted below and described in more detail in the following sections.

              

Importing Objective-C into Swift:

To import a set of Objective-C files in the same app target as your Swift code, you rely on an Objective-C bridging header to expose those files to Swift. Xcode offers to create this header file when you add a Swift file to an existing Objective-C app, or an Objective-C file to an existing Swift app.

                         

If you accept, Xcode creates the header file along with the file you were creating, and names it by your product module name followed by adding "-Bridging-Header.h". For information on the product module name, see Naming Your Product Module.

You'll need to edit this file to expose your Objective-C code to your Swift code.

To import Objective-C code into Swift from the same target
  
1. In your Objective-C bridging header file, import every Objective-C header you want to expose to Swift. For example:

    Objective-C

    i.   #import "XYZCustomCell.h"
    ii.  #import "XYZCustomView.h"
    iii. #import "XYZCustomViewController.h"

2. Under Build Settings, make sure the Objective-C Bridging Header build setting under Swift Compiler - Code Generation has a path to the header.

The Path should be relative to your project, similar to the way your info.plist path is specified in Build Settings. In most cases, you should not need to modify this setting.

Any public Objective-C headers listed in this bridging header file will be visible to Swift. The Objective-C functionality will be available in any Swift file within that target automatically, without any import statements. Use your custom Objective-C code with the same Swift syntax you use with system classes.

     Swift

1.   let myCell = XYZCustomCell( )
2.   myCell.subTitle = "A custom cell"

DHARANI KUMAR REDDY A

Calling a Method in iOS Swift: Takes and Returns multiple values

A function type can have a variadic parameter as the last parameter in its parameter type. Syntactically, a variadic parameter consists of a base type name followed immediately by three dots (...), as in Int.... A variadic parameter is treated as an array that contains elements of the base type name. For instance, the variadic parameter Int... is treated as [Int]. For an example that uses a variadic parameter, see Variadic Parameters.

To specify an in-out parameter, prefix the parameter type with the inout keyword. You can’t mark a variadic parameter or a return type with the inout keyword. In-out parameters are discussed in In-Out Parameters.

The type of a curried function is equivalent to a nested function type. For example, the type of the curried function addTwoNumbers()() below is (Int, Int) -> (Int, NSString, Int):

// Method Declaration in Swift Language:
func addTwoNumbers(a: Int, b: Int) -> (Int, NSString, BOOL)
{ 
return ((a + b), "Addition", True)
}

// Method Calling in Swift Language:
var (value, strValue, isTrue) = addTwoNumbers(4, 5) // Returns 9,Addition and TRUE

DHARANI KUMAR REDDY A