aboutsummaryrefslogtreecommitdiff
path: root/docs/cpp-coding/06-Considering_Portability.md
diff options
context:
space:
mode:
authorStefan Boberg <[email protected]>2022-04-05 17:22:17 +0200
committerGitHub <[email protected]>2022-04-05 17:22:17 +0200
commit9e0e00a9501d2b1e93a4237f313e3a955ccc2152 (patch)
tree0dc7e8b2e8b140925125d023d8411262db627274 /docs/cpp-coding/06-Considering_Portability.md
parentUpdate README.md (diff)
downloadzen-9e0e00a9501d2b1e93a4237f313e3a955ccc2152.tar.xz
zen-9e0e00a9501d2b1e93a4237f313e3a955ccc2152.zip
Delete docs directory
Diffstat (limited to 'docs/cpp-coding/06-Considering_Portability.md')
-rw-r--r--docs/cpp-coding/06-Considering_Portability.md21
1 files changed, 0 insertions, 21 deletions
diff --git a/docs/cpp-coding/06-Considering_Portability.md b/docs/cpp-coding/06-Considering_Portability.md
deleted file mode 100644
index 5fd89ef10..000000000
--- a/docs/cpp-coding/06-Considering_Portability.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Considering Portability
-
-## Know Your Types
-
-Most portability issues that generate warnings are because we are not careful about our types. Standard library and arrays are indexed with `size_t`. Standard container sizes are reported in `size_t`. If you get the handling of `size_t` wrong, you can create subtle lurking 64-bit issues that arise only after you start to overflow the indexing of 32-bit integers. char vs unsigned char.
-
-http://www.viva64.com/en/a/0010/
-
-## Use The Standard Library
-
-### `std::filesystem`
-
-C++17 added a new `filesystem` library which provides portable filesystem access across all supporting compilers
-
-### `std::thread`
-
-C++11's threading capabilities should be utilized over `pthread` or `WinThreads`.
-
-## Other Concerns
-
-Most of the other concerns in this document ultimately come back to portability issues. [Avoid statics](07-Considering_Threadability.md#statics) is particularly of note.