Book Image

Mastering macOS Programming.

By : Stuart Grimshaw, Gregory Casamento
Book Image

Mastering macOS Programming.

By: Stuart Grimshaw, Gregory Casamento

Overview of this book

macOS continues to lead the way in desktop operating systems, with its tight integration across the Apple ecosystem of platforms and devices. With this book, you will get an in-depth knowledge of working on macOS, enabling you to unleash the full potential of the latest version using Swift 3 to build applications. This book will help you broaden your horizons by taking your programming skills to next level. The initial chapters will show you all about the environment that surrounds a developer at the start of a project. It introduces you to the new features that Swift 3 and Xcode 8 offers and also covers the common design patterns that you need to know for planning anything more than trivial projects. You will then learn the advanced Swift programming concepts, including memory management, generics, protocol orientated and functional programming and with this knowledge you will be able to tackle the next several chapters that deal with Apple’s own Cocoa frameworks. It also covers AppKit, Foundation, and Core Data in detail which is a part of the Cocoa umbrella framework. The rest of the book will cover the challenges posed by asynchronous programming, error handling, debugging, and many other areas that are an indispensable part of producing software in a professional environment. By the end of this book, you will be well acquainted with Swift, Cocoa, and AppKit, as well as a plethora of other essential tools, and you will be ready to tackle much more complex and advanced software projects.
Table of Contents (28 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
18
LLDB and the Command Line

Errors aren't mistakes


But our errors are different in two fundamental ways. The first is that they contain information - as much information as you want. The second is that when they occur, you have a lot of flexibility as to what to do about them. They're like the Marine Corps of code-branching statements; when something unanticipated crops up, just stand back and let the specialists take over. Errors aren't mistakes, they are solutions.

None of which you can say for your math assignments.

But who wants to be delving into error handling when we could be animating the transition of a table view cell into a web-browsing-enabled emoji? Are errors not inherently unattractive? Does error handling mean that we're lousy developers really? Can we just leave this for later and get on with using the Core3DAugmentedSocialVideo framework?

As a result of their understandably less-than-stellar image, errors are not only poorly understood, they are also chronically underused, and it is the intention of...