Book Image

Mastering macOS Programming.

By : Gregory Casamento
Book Image

Mastering macOS Programming.

By: 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

Expecting the unexpected


Programming was challenging enough in the days when scientists in lab coats were writing code for their own use on a single mainframe computer located in a cellar just a few meters away.

But the apps that we write - that you write - today, now run on thousands or millions of machines, operated by thousands or millions of users, who are connected to millions or billions of other machines. There is simply no way that all those users and connections are going to behave themselves, and as for the other developers (who are filling servers all over the globe with code that has to deal with millions of apps like yours) that expect to have things their own way, well, you can imagine, it's a bit of a jungle out there.

So, we need to deal with unanticipated situations occurring constantly. We need strategies to deal with one piece of code being told to do something it can't that will keep our apps running smoothly and predictably when something says:

Sorry, it didn't work out...