Skip to content

Commit 2ba56ad

Browse files
authored
Trim front and back spaces in link destinations
1 parent 087e22d commit 2ba56ad

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

docs/cpp/results-of-calling-example.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ The **`__cdecl`** calling convention
2020

2121
The C decorated name (**`__stdcall`**) is `_MyFunc@20`. The C++ decorated name is implementation-specific.
2222

23-
![Diagram showing the stack and registers for the S T D call and this call calling conventions.](../cpp/media/vc37i02.gif )<br/>
23+
![Diagram showing the stack and registers for the S T D call and this call calling conventions.](../cpp/media/vc37i02.gif)<br/>
2424
The __stdcall and thiscall calling conventions
2525

2626
## `__fastcall`

docs/linux/cmake-linux-configure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ To target WSL, select **Manage Configurations** in the configuration dropdown in
130130

131131
The **CMakeSettings.json** window appears.
132132

133-
![CMake settings dialog with the plus button highlighted which adds the selected configuration, which is Linux-GCC-debug.](media/cmake-linux-configurations.png )
133+
![CMake settings dialog with the plus button highlighted which adds the selected configuration, which is Linux-GCC-debug.](media/cmake-linux-configurations.png)
134134

135135
Press **Add Configuration** (the green '+' button) and then choose **Linux-GCC-Debug** or **Linux-GCC-Release** if using GCC. Use the Clang variants if you're using the Clang/LLVM toolset. Press **Select** and then **Ctrl+S** to save the configuration.
136136

docs/overview/overview-of-cpp-development.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,13 +44,13 @@ Source control enables you to coordinate work among multiple developers, isolate
4444

4545
::: moniker range=">=msvc-160"
4646

47-
![Screenshot of the Team Explorer window in Visual Studio 2019.](media/vs2019-team-explorer.png )
47+
![Screenshot of the Team Explorer window in Visual Studio 2019.](media/vs2019-team-explorer.png)
4848

4949
::: moniker-end
5050

5151
::: moniker range="<=msvc-150"
5252

53-
![Screenshot of the Team Explorer window in Visual Studio 2017.](media/vs2017-team-explorer.png )
53+
![Screenshot of the Team Explorer window in Visual Studio 2017.](media/vs2017-team-explorer.png)
5454

5555
::: moniker-end
5656

docs/porting/fix-your-dependencies-on-library-internals.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,13 @@ In most cases, the What's New or Breaking Changes document for each release of V
1313

1414
## _Hash_seq
1515

16-
The internal hash function `std::_Hash_seq(const unsigned char *, size_t)`, used to implement `std::hash` on some string types, was visible in recent versions of the Standard Library. This function implemented an [FNV-1a hash]( https://en.wikipedia.org/wiki/Fowler%E2%80%93Noll%E2%80%93Vo_hash_function) on a character sequence.
16+
The internal hash function `std::_Hash_seq(const unsigned char *, size_t)`, used to implement `std::hash` on some string types, was visible in recent versions of the Standard Library. This function implemented an [FNV-1a hash](https://en.wikipedia.org/wiki/Fowler%E2%80%93Noll%E2%80%93Vo_hash_function) on a character sequence.
1717

1818
To remove this dependency, you have a couple of options.
1919

2020
- If your intent is to put a `const char *` sequence into an unordered container by using the same hash code machinery as `basic_string`, you can do that by using the `std::hash` template overload that takes a `std::string_view`, which returns that hash code in a portable way. The string library code may or may not rely on use of an FNV-1a hash in the future, so this is the best way to avoid a dependency on a particular hash algorithm.
2121

22-
- If your intent is to generate an FNV-1a hash over arbitrary memory, we've made that code available on GitHub in the [VCSamples]( https://github.com/Microsoft/vcsamples) repository in a stand-alone header file, [fnv1a.hpp](https://github.com/Microsoft/VCSamples/tree/master/VC2015Samples/_Hash_seq), under an [MIT license](https://github.com/Microsoft/VCSamples/blob/master/license.txt). We've also included a copy here for your convenience. You can copy this code into a header file, add the header to any affected code, and then find and replace `_Hash_seq` by `fnv1a_hash_bytes`. You'll get identical behavior to the internal implementation in `_Hash_seq`.
22+
- If your intent is to generate an FNV-1a hash over arbitrary memory, we've made that code available on GitHub in the [VCSamples](https://github.com/Microsoft/vcsamples) repository in a stand-alone header file, [fnv1a.hpp](https://github.com/Microsoft/VCSamples/tree/master/VC2015Samples/_Hash_seq), under an [MIT license](https://github.com/Microsoft/VCSamples/blob/master/license.txt). We've also included a copy here for your convenience. You can copy this code into a header file, add the header to any affected code, and then find and replace `_Hash_seq` by `fnv1a_hash_bytes`. You'll get identical behavior to the internal implementation in `_Hash_seq`.
2323

2424
```cpp
2525
/*

0 commit comments

Comments
 (0)