You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Please remember to include platform information with your report. If the bug is
17
17
18
18
Before embarking on a large amount of work to implement missing functionality, please double-check with the community on the [swift-corelibs-dev](https://lists.swift.org/mailman/listinfo/swift-corelibs-dev) mailing list. Someone may already be working in this area, and we want to avoid duplication of work.
19
19
20
-
If your request includes functionality changes, please be sure to test your code on Linux as well as OS X. Differences in the compiler and runtime on each platform means that code that compiles and runs correctly on Darwin (where the Objective-C runtime is present) may not compile at all on Linux.
20
+
If your request includes functionality changes, please be sure to test your code on Linux as well as macOS. Differences in the compiler and runtime on each platform means that code that compiles and runs correctly on Darwin (where the Objective-C runtime is present) may not compile at all on Linux.
Copy file name to clipboardExpand all lines: Docs/Archiving.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# Archiving Notes
2
2
3
-
There is a preliminary implementation of NSKeyedArchiver and NSKeyedUnarchiver which should be compatible with the OS X version.
3
+
There is a preliminary implementation of NSKeyedArchiver and NSKeyedUnarchiver which should be compatible with the macOS version.
4
4
5
-
* NSKeyedUnarchiver reads the entire plist into memory before constructing the object graph, it should construct it incrementally as does Foundation on OS X
5
+
* NSKeyedUnarchiver reads the entire plist into memory before constructing the object graph, it should construct it incrementally as does Foundation on macOS
6
6
7
7
* Paths that raise errors vs. calling _fatalError() need to be reviewed carefully
Copy file name to clipboardExpand all lines: Docs/Design.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
4
4
## Portability
5
5
6
-
This version of Foundation is designed to support the same API as the Foundation that ships with Apple operating systems. A key difference is that the distribution of Swift open source does not include the Objective-C runtime. This means that the source code of Foundation from OS X and iOS could not be simply reused on other platforms. However, we believe that the vast majority of the core API concepts presented in Foundation are themselves portable and are useful on all platforms.
6
+
This version of Foundation is designed to support the same API as the Foundation that ships with Apple operating systems. A key difference is that the distribution of Swift open source does not include the Objective-C runtime. This means that the source code of Foundation from macOS and iOS could not be simply reused on other platforms. However, we believe that the vast majority of the core API concepts presented in Foundation are themselves portable and are useful on all platforms.
7
7
8
8
It is not a goal of this project to create new API that extends beyond the API provided on Apple operating systems, as that would hamper the goal of portability.
9
9
@@ -85,7 +85,7 @@ When different logic is required for the Swift runtime in CF, use the following
85
85
86
86
In Swift, the OS-check macro is also available:
87
87
```swift
88
-
#ifos(OSX) ||os(iOS)
88
+
#ifos(macOS) ||os(iOS)
89
89
importDarwin
90
90
#elseifos(Linux)
91
91
importGlibc
@@ -113,7 +113,7 @@ One of the main challenges of developing and maintaining a widely used library i
113
113
114
114
## Keeping Organized
115
115
116
-
Parts of the CoreFoundation and Foundation libraries are as old as OS X (or older). In order to support long-term maintainability, it is important to keep our source code organized.
116
+
Parts of the CoreFoundation and Foundation libraries are as old as macOS (or older). In order to support long-term maintainability, it is important to keep our source code organized.
117
117
118
118
* If it helps keep an effective separation of concerns, feel free to split up functionality of one class over several files.
119
119
* If appropriate, use `// MARK - Topic` to split up sections of a file.
Copy file name to clipboardExpand all lines: Foundation/Data.swift
+2-2
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@
12
12
13
13
#if DEPLOYMENT_RUNTIME_SWIFT
14
14
15
-
#if os(OSX) || os(iOS)
15
+
#if os(macOS) || os(iOS)
16
16
import Darwin
17
17
#elseif os(Linux)
18
18
import Glibc
@@ -1391,7 +1391,7 @@ public struct Data : ReferenceConvertible, Equatable, Hashable, RandomAccessColl
1391
1391
1392
1392
// Avoid a crash that happens on OS X 10.11.x and iOS 9.x or before when writing a bridged Data non-atomically with Foundation's standard write() implementation.
0 commit comments