Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Swift 3

You're reading from   Mastering Swift 3 Build incredible apps for iOS and OS X

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781786466129
Length 392 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Jon Hoffman Jon Hoffman
Author Profile Icon Jon Hoffman
Jon Hoffman
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Taking the First Steps with Swift 2. Learning About Variables, Constants, Strings, and Operators FREE CHAPTER 3. Using Swift Collections and the Tuple Type 4. Control Flow and Functions 5. Classes and Structures 6. Using Protocols and Protocol Extensions 7. Protocol-Oriented Design 8. Writing Safer Code with Availability and Error Handling 9. Custom Subscripting 10. Using Optional Types 11. Working with Generics 12. Working with Closures 13. Using Mix and Match 14. Concurrency and Parallelism in Swift 15. Swift Formatting and Style Guide 16. Swifts Core Libraries 17. Adopting Design Patterns in Swift

Native error handling


Languages such as Java and C# generally refer to the error handling process as exception handling; within the Swift documentation, Apple refers to this process as error handling. While on the outside, the Java and C# exception handling may look somewhat similar to Swift's error handling, there are some significant differences that those familiar with exception handling in the other language will notice throughout this chapter.

Representing errors

Before we can really understand how error handling works in Swift, we must see how we would represent an error. In Swift, errors are represented by values of types that conform to the Error protocol. Swift's enumerations are very well-suited to modeling error conditions because generally we have a finite number of error conditions to represent.

Let's look at how we would use an enumeration to represent an error. For this, we will define a fictitious error named MyError with three error conditions, Minor, Bad, and Terrible:

enum...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image