swift can catch fatal error?

I am trying to use Swift 2.0 try-catch.

I originally had the following code

  • xCode - UIVisualEffectView animating
  • Next/Done button using Swift with textFieldShouldReturn
  • Change User-Agent
  • Debugging crash in CoreGraphics/MapKit
  • What is GCC_NO_COMMON_BLOCKS used for?
  • Why are Objective-C delegates usually given the property assign instead of retain?
  • override func viewDidLoad()
    {
        var obj : Object?;
        Hi( obj );
    }
    

    But it procdues an error

    func Hi( open : Open? ) -> Open?
    {
        open!.Hi(); <-- here is error point. Fatal error !
        print( "OK" );
    
        return open;
    }
    

    Therefore I changed the code in viewDidLoad() to:

    override func viewDidLoad()
    {
        try
        {
            var obj : Object?;
            Hi( obj );
        }
        catch
        {
            print( "bug !!!" ); <- I want to this !!!
        }
    }
    

    But it does not work !!!

    I guess swift‘s try-catch is different than in C, C#.

    How can I catch the fatal error ?

    Might the following be a proper swift way?

    func Hi( open : Open? ) -> Open?
    {
        if let op = open
        {
            op.Hi();
            print( "OK" );
    
            return open;
        }
        else
        {
            return nil;
        }
    }
    

    2 Solutions Collect From Internet About “swift can catch fatal error?”

    You are not supposed to catch fatalerror. It indicates a programming error. You don’t catch programming errors, you fix your code. The crash is intentional and it is intentional that you cannot stop it.

    Something involving the keywords try, catch and throw is available in Swift 2, but that is nothing like C++ exceptions that you seem to be thinking about.

    When you’re calling Hi() like this: open!.Hi();, your program can crash if open is nil.

    open is a parameter, and the value that is passed as that parameter is defined on the call site as such: var obj : Object?;. You’re defining a new variable named obj with type Object?, but you’re not assigning it a value. This means that obj will be nil and therefore open will be nil and this leads to open!.Hi() crashing.

    To solve it, make sure to assign a value to the parameter of Hi. It might be better to make the parameter non-optional as well, so you don’t have to force unwrap it to call a function on it.