Skip to content

Commit 5ef9f4f

Browse files
committed
Clarify about Windows functions with explicit ABI
Some Windows API functions have an explicitly defined ABI. We were trying to suggest this with wording that was a bit subtle; let's spell it out explicitly.
1 parent a78b6c2 commit 5ef9f4f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/items/external-blocks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ r[items.extern.abi.system]
127127
* `unsafe extern "system"` --- This is equivalent to `extern "C"` except on Windows x86_32 where it is equivalent to `"stdcall"`.
128128
129129
> [!NOTE]
130-
> As the correct underlying ABI on Windows is target-specific, it's best to use `extern "system"` when attempting to link Windows API functions that don't otherwise use a different ABI.
130+
> As the correct underlying ABI on Windows is target-specific, it's best to use `extern "system"` when attempting to link Windows API functions that don't use an explicitly defined ABI.
131131
132132
r[items.extern.abi.unwind]
133133
* `extern "C-unwind"` and `extern "system-unwind"` --- Identical to `"C"` and `"system"`, respectively, but with [different behavior][unwind-behavior] when the callee unwinds (by panicking or throwing a C++ style exception).

0 commit comments

Comments
 (0)