Skip to content

Add best practice for avoiding native symbol name collisions #9484

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 3, 2023
Merged

Add best practice for avoiding native symbol name collisions #9484

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
53b049c
Add best practice for avoiding native symbol name collisions
jkotas Dec 1, 2023
bb9e354
Update xml/System.Runtime.InteropServices/UnmanagedCallersOnlyAttribu…
jkotas Dec 1, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions xml/System.Runtime.InteropServices/UnmanagedCallersOnlyAttribute.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,7 @@ Supplied types must be from the official <xref:System.Runtime.CompilerServices>
## Remarks

The export name must be a valid identifier for a native symbol on the target platform. The identifier must not conflict with system-provided native identifiers (for example, names of methods in the C standard library, or POSIX/Win32 API names).
Using a prefix for symbols is a common way to avoid name collisions of native symbols. For example, you can name the exported functions as `mylibrary_free`, `mylibrary_isdigit` and `mylibrary_copy` to avoid name collisions.

Target-dependent name mangling will be performed on the symbol name such as prepending or appending `_` or `@` characters to distinguish calling conventions on x86 Windows.

Expand Down