Skip to content

Commit e98888c

Browse files
author
Colin Robertson
authored
Merge pull request #25 from Mixaill/patch-1
importing-using-def-files.md: fix typo
2 parents bd29d47 + 52f00ad commit e98888c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/build/importing-using-def-files.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ EXPORTS
5050

5151
|Keyword|Emits in the import library|Exports|
5252
|-------------|---------------------------------|-------------|
53-
|`CONSTANT`|`_imp_ulDataInDll_ulDataInDll`|`_ulDataInDll`|
53+
|`CONSTANT`|`_imp_ulDataInDll`, `_ulDataInDll`|`_ulDataInDll`|
5454
|`DATA`|`_imp_ulDataInDll`|`_ulDataInDll`|
5555

5656
Using **__declspec(dllimport)** and CONSTANT lists both the `imp` version and the undecorated name in the .lib DLL import library that is created to allow explicit linking. Using **__declspec(dllimport)** and DATA lists just the `imp` version of the name.
@@ -82,4 +82,4 @@ if (ulDataInDll == 0L) /*sample code fragment*/
8282
The current Visual C++ linker issues a warning if it sees CONSTANT in the .def file to account for this case. The only real reason to use CONSTANT is if you cannot recompile some object file where the header file did not list **__declspec(dllimport)** on the prototype.
8383

8484
## See Also
85-
[Importing into an Application](../build/importing-into-an-application.md)
85+
[Importing into an Application](../build/importing-into-an-application.md)

0 commit comments

Comments
 (0)