If we comment out a block of code while we attempt to replace it, once we are comfortable with the changes we should remove the code that we commented out. Having large blocks of code commented out can make the code base look messy and harder to follow.
Don't leave commented-out code in your application
by Jon Hoffman
Mastering Swift 4 - Fourth Edition
- Preface
- Taking the First Steps with Swift
- What is Swift?
- Playgrounds
- Getting started with Playgrounds
- iOS, tvOS, and macOS Playgrounds
- Showing images in a Playground
- Creating and displaying graphs in Playgrounds
- What Playgrounds are not
- Swift language syntax
- Comments
- Semicolons
- Parentheses
- Curly brackets
- An assignment operator does not return a value
- Spaces are optional in conditional and assignment statements
- Hello World
- Summary
- Learning about Variables, Constants, Strings, and Operators
- Using Swift Collections and the Tuple Type
- Swift collection types
- Mutability
- Arrays
- Creating and initializing arrays
- Accessing the array elements
- Counting the elements of an array
- Is the array empty?
- Appending to an array
- Inserting a value into an array
- Replacing elements in an array
- Removing elements from an array
- Merging two arrays
- Retrieving a subarray from an array
- Making bulk changes to an array
- Algorithms for arrays
- Iterating over an array
- Dictionaries
- Set
- Tuples
- Summary
- Control Flow and Functions
- Classes and Structures
- Using Protocols and Protocol Extensions
- Protocol-Oriented Design
- Writing Safer Code with Availability and Error Handling
- Custom Subscripting
- Using Optional Types
- Working with Generics
- Working with Closures
- Using Mix and Match
- What is mix and match?
- When to use mix and match
- Using Swift and Objective-C together in the same project
- Creating the project
- Adding Swift files to the Objective-C project
- The Objective-C bridging header file - part 1
- Adding the Objective-C file to the project
- The Messages Objective-C class
- The Objective-C bridging header file - part 2
- The MessageBuilder Swift class - accessing Objective-C code from Swift
- The Objective-C class - accessing Swift code from Objective-C
- Summary
- Concurrency and Parallelism in Swift
- Swift Formatting and Style Guide
- What is a programming style guide?
- Your style guide
- Do not use semicolons at the end of statements
- Do not use parentheses for conditional statements
- Naming
- Comments
- Using the self keyword
- Constants and variables
- Optional types
- Using type inference
- Using shorthand declaration for collections
- Using switch rather than multiple if statements
- Don't leave commented-out code in your application
- Summary
- Swift Core Libraries
- Adopting Design Patterns in Swift
Don't leave commented-out code in your application
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.