You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This class provides a default implementation of the [ISupportErrorInfo Interface](/windows/desktop/api/oaidl/nn-oaidl-isupporterrorinfo) and can be used when only a single interface generates errors on an object.
11
11
12
12
> [!IMPORTANT]
13
-
> This class and its members cannot be used in applications that execute in the Windows Runtime.
13
+
> This class and its members cannot be used in applications that execute in the Windows Runtime.
14
14
15
15
## Syntax
16
16
17
-
```
17
+
```cpp
18
18
template<const IID* piid>
19
19
classATL_NO_VTABLE ISupportErrorInfoImpl
20
20
: public ISupportErrorInfo
21
21
```
22
22
23
-
####Parameters
23
+
### Parameters
24
24
25
25
*piid*<br/>
26
26
A pointer to the IID of an interface that supports [IErrorInfo](/windows/desktop/api/oaidl/nn-oaidl-ierrorinfo).
@@ -55,102 +55,14 @@ Class `ISupportErrorInfoImpl` provides a default implementation of `ISupportErro
55
55
56
56
Indicates whether the interface identified by `riid` supports the [IErrorInfo](/windows/desktop/api/oaidl/nn-oaidl-ierrorinfo) interface.
See [ISupportErrorInfo::InterfaceSupportsErrorInfo](/windows/desktop/api/oaidl/nf-oaidl-isupporterrorinfo-interfacesupportserrorinfo) in the Windows SDK.
Call this method to set the number of threads in the pool.
111
-
112
-
```
113
-
STDMETHOD(SetSize)int nNumThreads);
114
-
```
115
-
116
-
### Parameters
117
-
118
-
*nNumThreads*<br/>
119
-
The requested number of threads in the pool.
120
-
121
-
If *nNumThreads* is negative, its absolute value will be multiplied by the number of processors in the machine to get the total number of threads.
122
-
123
-
If *nNumThreads* is zero, ATLS_DEFAULT_THREADSPERPROC will be multiplied by the number of processors in the machine to get the total number of threads.
124
-
125
-
### Return Value
126
-
127
-
Returns S_OK on success, or an error HRESULT on failure.
The linker sends information about the progress of the linking session to the **Output** window. On the command line, the information is sent to standard output and can be redirected to a file.
18
+
The linker sends information about the progress of the linking session to the **Output** window. On the command line, the information is sent to standard output, and can be redirected to a file.
17
19
18
-
|Option|Description|
19
-
|------------|-----------------|
20
-
|/VERBOSE|Displays details about the linking process.|
21
-
|/VERBOSE:ICF|Display information about linker activity that results from the use of [/OPT:ICF](opt-optimizations.md).|
22
-
|/VERBOSE:INCR|Displays information about the incremental link process.|
23
-
|/VERBOSE:LIB|Displays progress messages that indicate just the libraries searched.<br /><br /> The displayed information includes the library search process and lists each library and object name (with full path), the symbol being resolved from the library, and a list of objects that reference the symbol.|
24
-
|/VERBOSE:REF|Displays information about linker activity that results from the use of [/OPT:REF](opt-optimizations.md).|
25
-
|/VERBOSE:SAFESEH|Displays information about modules that are not compatible with safe exception handling when [/SAFESEH](safeseh-image-has-safe-exception-handlers.md) is not specified.|
26
-
|/VERBOSE:UNUSEDLIBS|Displays information about any library files that are unused when the image is created.|
20
+
| Option | Description |
21
+
| ------------ | ----------------- |
22
+
| /VERBOSE | Displays details about the linking process. |
23
+
| /VERBOSE:CLR| Displays information about linker activity specific to objects and metadata compiled by using [/clr](clr-common-language-runtime-compilation.md). |
24
+
| /VERBOSE:ICF| Displays information about linker activity that results from the use of [/OPT:ICF](opt-optimizations.md). |
25
+
| /VERBOSE:INCR| Displays information about the incremental link process. |
26
+
| /VERBOSE:LIB| Displays progress messages that indicate just the libraries searched.<br/> The displayed information includes the library search process. It lists each library and object name (with full path), the symbol being resolved from the library, and a list of objects that reference the symbol. |
27
+
| /VERBOSE:REF| Displays information about linker activity that results from the use of [/OPT:REF](opt-optimizations.md). |
28
+
| /VERBOSE:SAFESEH| Displays information about modules that are incompatible with safe structured exception handling when [/SAFESEH](safeseh-image-has-safe-exception-handlers.md) isn't specified. |
29
+
| /VERBOSE:UNUSEDDELAYLOAD| Displays information about any delay loaded DLLs that have no symbols used when the image is created. |
30
+
| /VERBOSE:UNUSEDLIBS| Displays information about any library files that are unused when the image is created. |
27
31
28
32
### To set this linker option in the Visual Studio development environment
29
33
30
34
1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
Copy file name to clipboardExpand all lines: docs/cpp/references-to-pointers.md
+16-16Lines changed: 16 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
---
2
-
title: "References to Pointers"
3
-
ms.date: "08/20/2018"
2
+
title: "References to pointers"
3
+
ms.date: "06/13/2019"
4
4
helpviewer_keywords: ["references, to pointers"]
5
5
ms.assetid: 4ce48b08-1511-4d2f-a31f-95f99eac0c70
6
6
---
7
-
# References to Pointers
7
+
# References to pointers
8
8
9
-
References to pointers can be declared in much the same way as references to objects. Declaring a reference to a pointer yields a modifiable value that is used like a normal pointer.
9
+
References to pointers can be declared in much the same way as references to objects. A reference to a pointer is a modifiable value that's used like a normal pointer.
10
10
11
11
## Example
12
12
13
-
The following code samples illustrate the difference between using a pointer to a pointer and a reference to a pointer.
13
+
This code sample shows the difference between using a pointer to a pointer and a reference to a pointer.
14
14
15
-
Functions `Add1` and `Add2` are functionally equivalent (although they are not called the same way). The difference is that `Add1` uses double indirection whereas`Add2` uses the convenience of a reference to a pointer.
15
+
Functions `Add1` and `Add2` are functionally equivalent, although they're not called the same way. The difference is that `Add1` uses double indirection, but`Add2` uses the convenience of a reference to a pointer.
0 commit comments