Skip to content

Commit 4bce7e2

Browse files
ghogenghogen
committed
Comment out and/or fix code reference and token/include errors
1 parent 6f63a4f commit 4bce7e2

15 files changed

+366
-760
lines changed

‎docs/atl-mfc-shared/reference/cimage-class.md‎

Lines changed: 20 additions & 20 deletions
Large diffs are not rendered by default.

‎docs/atl-mfc-shared/reference/crect-class.md‎

Lines changed: 30 additions & 30 deletions
Large diffs are not rendered by default.

‎docs/atl/reference/ccommultithreadmodel-class.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ typedef CComAutoCriticalSection AutoCriticalSection;
101101
### Example
102102
The following code is modeled after [CComObjectRootEx](../Topic/CComObjectRootEx%20Class.md), and demonstrates `AutoCriticalSection` being used in a threading environment.
103103

104-
[!CODE [NVC_ATL_COM#36](../CodeSnippet/VS_Snippets_Cpp/NVC_ATL_COM#36)]
104+
<!-- FIXME [!CODE [NVC_ATL_COM#36](../CodeSnippet/VS_Snippets_Cpp/NVC_ATL_COM#36)] -->
105105

106106
The following tables show the results of the `InternalAddRef` and `Lock` methods, depending on the **ThreadModel** template parameter and the threading model used by the application:
107107

‎docs/cpp/how-to-create-and-use-shared-ptr-instances.md‎

Lines changed: 35 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,37 @@
1-
---
2-
title: "How to: Create and Use shared_ptr Instances | Microsoft Docs"
3-
ms.custom: ""
4-
ms.date: "11/04/2016"
5-
ms.prod: "visual-studio-dev14"
6-
ms.reviewer: ""
7-
ms.suite: ""
8-
ms.technology:
9-
- "devlang-cpp"
10-
ms.tgt_pltfrm: ""
11-
ms.topic: "article"
12-
dev_langs:
13-
- "C++"
14-
ms.assetid: 7d6ebb73-fa0d-4b0b-a528-bf05de96518e
15-
caps.latest.revision: 15
16-
author: "mikeblome"
17-
ms.author: "mblome"
18-
manager: "ghogen"
19-
translation.priority.ht:
20-
- "cs-cz"
21-
- "de-de"
22-
- "es-es"
23-
- "fr-fr"
24-
- "it-it"
25-
- "ja-jp"
26-
- "ko-kr"
27-
- "pl-pl"
28-
- "pt-br"
29-
- "ru-ru"
30-
- "tr-tr"
31-
- "zh-cn"
32-
- "zh-tw"
33-
---
34-
# How to: Create and Use shared_ptr Instances
1+
---
2+
title: "How to: Create and Use shared_ptr Instances | Microsoft Docs"
3+
ms.custom: ""
4+
ms.date: "11/04/2016"
5+
ms.prod: "visual-studio-dev14"
6+
ms.reviewer: ""
7+
ms.suite: ""
8+
ms.technology:
9+
- "devlang-cpp"
10+
ms.tgt_pltfrm: ""
11+
ms.topic: "article"
12+
dev_langs:
13+
- "C++"
14+
ms.assetid: 7d6ebb73-fa0d-4b0b-a528-bf05de96518e
15+
caps.latest.revision: 15
16+
author: "mikeblome"
17+
ms.author: "mblome"
18+
manager: "ghogen"
19+
translation.priority.ht:
20+
- "cs-cz"
21+
- "de-de"
22+
- "es-es"
23+
- "fr-fr"
24+
- "it-it"
25+
- "ja-jp"
26+
- "ko-kr"
27+
- "pl-pl"
28+
- "pt-br"
29+
- "ru-ru"
30+
- "tr-tr"
31+
- "zh-cn"
32+
- "zh-tw"
33+
---
34+
# How to: Create and Use shared_ptr Instances
3535
The `shared_ptr` type is a smart pointer in the C++ standard library that is designed for scenarios in which more than one owner might have to manage the lifetime of the object in memory. After you initialize a `shared_ptr` you can copy it, pass it by value in function arguments, and assign it to other `shared_ptr` instances. All the instances point to the same object, and share access to one "control block" that increments and decrements the reference count whenever a new `shared_ptr` is added, goes out of scope, or is reset. When the reference count reaches zero, the control block deletes the memory resource and itself.
3636

3737
The following illustration shows several `shared_ptr` instances that point to one memory location.
@@ -73,7 +73,7 @@ The `shared_ptr` type is a smart pointer in the C++ standard library that is des
7373

7474
- Sometimes, for example in a `std:vector<shared_ptr<T>>`, you may have to pass each `shared_ptr` to a lambda expression body or named function object. If the lambda or function is not storing the pointer, then pass the `shared_ptr` by reference to avoid invoking the copy constructor for each element.
7575

76-
[!CODE [stl_smart_pointers#6](../CodeSnippet/VS_Snippets_Cpp/stl_smart_pointers#6)]
76+
<!-- FIXME [!CODE [stl_smart_pointers#6](../CodeSnippet/VS_Snippets_Cpp/stl_smart_pointers#6)] -->
7777

7878
## Example
7979
The following example shows how `shared_ptr` overloads various comparison operators to enable pointer comparisons on the memory that is owned by the `shared_ptr` instances.

‎docs/data/oledb/begin-accessor-map.md‎

Lines changed: 36 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -37,40 +37,40 @@ translation.priority.mt:
3737
- "tr-tr"
3838
---
3939
# BEGIN_ACCESSOR_MAP
40-
Marks the beginning of the accessor map entries.
41-
42-
## Syntax
43-
44-
```
45-
46-
BEGIN_ACCESSOR_MAP(
47-
x
48-
,
49-
num
50-
)
51-
52-
```
53-
54-
#### Parameters
55-
*x*
56-
[in] The name of the user record class.
57-
58-
*num*
59-
[in] The number of accessors in this accessor map.
60-
61-
## Remarks
62-
In the case of multiple accessors on a rowset, you need to specify `BEGIN_ACCESSOR_MAP` at the beginning and use the `BEGIN_ACCESSOR` macro for each individual accessor. The `BEGIN_ACCESSOR` macro is completed with the `END_ACCESSOR` macro. The accessor map is completed with the `END_ACCESSOR_MAP` macro.
63-
64-
If you have only one accessor in the user record, use the macro [BEGIN_COLUMN_MAP](../../data/oledb/begin-column-map.md).
65-
66-
## Example
67-
[!CODE [NVC_OLEDB_Consumer#15](../CodeSnippet/VS_Snippets_Cpp/NVC_OLEDB_Consumer#15)]
68-
69-
## Requirements
70-
**Header:** atldbcli.h
71-
72-
## See Also
73-
[Macros and Global Functions for OLE DB Consumer Templates](../../data/oledb/macros-and-global-functions-for-ole-db-consumer-templates.md)
74-
[BEGIN_ACCESSOR](../../data/oledb/begin-accessor.md)
75-
[END_ACCESSOR](../../data/oledb/end-accessor.md)
40+
Marks the beginning of the accessor map entries.
41+
42+
## Syntax
43+
44+
```
45+
46+
BEGIN_ACCESSOR_MAP(
47+
x
48+
,
49+
num
50+
)
51+
52+
```
53+
54+
#### Parameters
55+
*x*
56+
[in] The name of the user record class.
57+
58+
*num*
59+
[in] The number of accessors in this accessor map.
60+
61+
## Remarks
62+
In the case of multiple accessors on a rowset, you need to specify `BEGIN_ACCESSOR_MAP` at the beginning and use the `BEGIN_ACCESSOR` macro for each individual accessor. The `BEGIN_ACCESSOR` macro is completed with the `END_ACCESSOR` macro. The accessor map is completed with the `END_ACCESSOR_MAP` macro.
63+
64+
If you have only one accessor in the user record, use the macro [BEGIN_COLUMN_MAP](../../data/oledb/begin-column-map.md).
65+
66+
## Example
67+
<!-- FIXME [!CODE [NVC_OLEDB_Consumer#15](../CodeSnippet/VS_Snippets_Cpp/NVC_OLEDB_Consumer#15)] -->
68+
69+
## Requirements
70+
**Header:** atldbcli.h
71+
72+
## See Also
73+
[Macros and Global Functions for OLE DB Consumer Templates](../../data/oledb/macros-and-global-functions-for-ole-db-consumer-templates.md)
74+
[BEGIN_ACCESSOR](../../data/oledb/begin-accessor.md)
75+
[END_ACCESSOR](../../data/oledb/end-accessor.md)
7676
[END_ACCESSOR_MAP](../../data/oledb/end-accessor-map.md)

‎docs/data/oledb/begin-column-map.md‎

Lines changed: 35 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -37,39 +37,39 @@ translation.priority.mt:
3737
- "tr-tr"
3838
---
3939
# BEGIN_COLUMN_MAP
40-
Marks the beginning of a column map entry.
41-
42-
## Syntax
43-
44-
```
45-
46-
BEGIN_COLUMN_MAP(
47-
x
48-
)
49-
50-
```
51-
52-
#### Parameters
53-
*x*
54-
[in] The name of the user record class derived from `CAccessor`.
55-
56-
## Remarks
57-
This macro is used in the case of a single accessor on a rowset. If you have multiple accessors on a rowset, use [BEGIN_ACCESSOR_MAP](../../data/oledb/begin-accessor-map.md).
58-
59-
The `BEGIN_COLUMN_MAP` macro is completed with the `END_COLUMN_MAP` macro. This macro is used when there is only one accessor required in the user record.
60-
61-
Columns correspond to fields in the rowset you want to bind.
62-
63-
## Example
64-
Here is a sample column and parameter map:
65-
66-
[!CODE [NVC_OLEDB_Consumer#16](../CodeSnippet/VS_Snippets_Cpp/NVC_OLEDB_Consumer#16)]
67-
68-
## Requirements
69-
**Header:** atldbcli.h
70-
71-
## See Also
72-
[Macros and Global Functions for OLE DB Consumer Templates](../../data/oledb/macros-and-global-functions-for-ole-db-consumer-templates.md)
73-
[END_COLUMN_MAP](../../data/oledb/end-column-map.md)
74-
[COLUMN_ENTRY](../../data/oledb/column-entry.md)
40+
Marks the beginning of a column map entry.
41+
42+
## Syntax
43+
44+
```
45+
46+
BEGIN_COLUMN_MAP(
47+
x
48+
)
49+
50+
```
51+
52+
#### Parameters
53+
*x*
54+
[in] The name of the user record class derived from `CAccessor`.
55+
56+
## Remarks
57+
This macro is used in the case of a single accessor on a rowset. If you have multiple accessors on a rowset, use [BEGIN_ACCESSOR_MAP](../../data/oledb/begin-accessor-map.md).
58+
59+
The `BEGIN_COLUMN_MAP` macro is completed with the `END_COLUMN_MAP` macro. This macro is used when there is only one accessor required in the user record.
60+
61+
Columns correspond to fields in the rowset you want to bind.
62+
63+
## Example
64+
Here is a sample column and parameter map:
65+
66+
<!--[!CODE [NVC_OLEDB_Consumer#16](../CodeSnippet/VS_Snippets_Cpp/NVC_OLEDB_Consumer#16)] -->
67+
68+
## Requirements
69+
**Header:** atldbcli.h
70+
71+
## See Also
72+
[Macros and Global Functions for OLE DB Consumer Templates](../../data/oledb/macros-and-global-functions-for-ole-db-consumer-templates.md)
73+
[END_COLUMN_MAP](../../data/oledb/end-column-map.md)
74+
[COLUMN_ENTRY](../../data/oledb/column-entry.md)
7575
[COLUMN_ENTRY_EX](../../data/oledb/column-entry-ex.md)

‎docs/data/oledb/bookmark-entry.md‎

Lines changed: 25 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -36,29 +36,29 @@ translation.priority.ht:
3636
- "zh-tw"
3737
---
3838
# BOOKMARK_ENTRY
39-
Binds the bookmark column.
40-
41-
## Syntax
42-
43-
```
44-
45-
BOOKMARK_ENTRY(
46-
variable
47-
)
48-
49-
```
50-
51-
#### Parameters
52-
*variable*
53-
[in] The variable to be bound to the bookmark column.
54-
55-
## Example
56-
[!CODE [NVC_OLEDB_Consumer#17](../CodeSnippet/VS_Snippets_Cpp/NVC_OLEDB_Consumer#17)]
57-
58-
## Requirements
59-
**Header:** atldbcli.h
60-
61-
## See Also
62-
[Macros and Global Functions for OLE DB Consumer Templates](../../data/oledb/macros-and-global-functions-for-ole-db-consumer-templates.md)
63-
[CBookmark Class](../../data/oledb/cbookmark-class.md)
39+
Binds the bookmark column.
40+
41+
## Syntax
42+
43+
```
44+
45+
BOOKMARK_ENTRY(
46+
variable
47+
)
48+
49+
```
50+
51+
#### Parameters
52+
*variable*
53+
[in] The variable to be bound to the bookmark column.
54+
55+
## Example
56+
<!-- FIXME [!CODE [NVC_OLEDB_Consumer#17](../CodeSnippet/VS_Snippets_Cpp/NVC_OLEDB_Consumer#17)] -->
57+
58+
## Requirements
59+
**Header:** atldbcli.h
60+
61+
## See Also
62+
[Macros and Global Functions for OLE DB Consumer Templates](../../data/oledb/macros-and-global-functions-for-ole-db-consumer-templates.md)
63+
[CBookmark Class](../../data/oledb/cbookmark-class.md)
6464
[DBPROP_BOOKMARKS](https://msdn.microsoft.com/en-us/library/ms709728.aspx)

‎docs/data/oledb/set-param-type.md‎

Lines changed: 34 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -37,38 +37,38 @@ translation.priority.mt:
3737
- "tr-tr"
3838
---
3939
# SET_PARAM_TYPE
40-
Specifies `COLUMN_ENTRY` macros that follow the `SET_PARAM_TYPE` macro input, output, or input/output.
41-
42-
## Syntax
43-
44-
```
45-
46-
SET_PARAM_TYPE(
47-
type
48-
)
49-
50-
```
51-
52-
#### Parameters
53-
`type`
54-
[in] The type to set for the parameter.
55-
56-
## Remarks
57-
Providers support only parameter input/output types that are supported by the underlying data source. The type is a combination of one or more **DBPARAMIO** values (see [DBBINDING Structures](https://msdn.microsoft.com/en-us/library/ms716845.aspx) in the *OLE DB Programmer's Reference*):
58-
59-
- **DBPARAMIO_NOTPARAM** The accessor has no parameters. Typically, you set **eParamIO** to this value in row accessors to remind the user that parameters are ignored.
60-
61-
- **DBPARAMIO_INPUT** An input parameter.
62-
63-
- **DBPARAMIO_OUTPUT** An output parameter.
64-
65-
- **DBPARAMIO_INPUT &#124; DBPARAMIO_OUTPUT** The parameter is both an input and an output parameter.
66-
67-
## Example
68-
[!CODE [NVC_OLEDB_Consumer#18](../CodeSnippet/VS_Snippets_Cpp/NVC_OLEDB_Consumer#18)]
69-
70-
## Requirements
71-
**Header:** atldbcli.h
72-
73-
## See Also
40+
Specifies `COLUMN_ENTRY` macros that follow the `SET_PARAM_TYPE` macro input, output, or input/output.
41+
42+
## Syntax
43+
44+
```
45+
46+
SET_PARAM_TYPE(
47+
type
48+
)
49+
50+
```
51+
52+
#### Parameters
53+
`type`
54+
[in] The type to set for the parameter.
55+
56+
## Remarks
57+
Providers support only parameter input/output types that are supported by the underlying data source. The type is a combination of one or more **DBPARAMIO** values (see [DBBINDING Structures](https://msdn.microsoft.com/en-us/library/ms716845.aspx) in the *OLE DB Programmer's Reference*):
58+
59+
- **DBPARAMIO_NOTPARAM** The accessor has no parameters. Typically, you set **eParamIO** to this value in row accessors to remind the user that parameters are ignored.
60+
61+
- **DBPARAMIO_INPUT** An input parameter.
62+
63+
- **DBPARAMIO_OUTPUT** An output parameter.
64+
65+
- **DBPARAMIO_INPUT &#124; DBPARAMIO_OUTPUT** The parameter is both an input and an output parameter.
66+
67+
## Example
68+
<!--FIXME[!CODE [NVC_OLEDB_Consumer#18](../CodeSnippet/VS_Snippets_Cpp/NVC_OLEDB_Consumer#18)]-->
69+
70+
## Requirements
71+
**Header:** atldbcli.h
72+
73+
## See Also
7474
[Macros and Global Functions for OLE DB Consumer Templates](../../data/oledb/macros-and-global-functions-for-ole-db-consumer-templates.md)

‎docs/mfc/reference/cexception-class.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ void Delete();
138138
You only need to call **Delete** if you are using the C++ **try**- **catch** mechanism. If you are using the MFC macros **TRY** and **CATCH**, then these macros will automatically call this function.
139139

140140
### Example
141-
[!CODE [NVC_MFCExceptions#21](../CodeSnippet/VS_Snippets_Cpp/NVC_MFCExceptions#21)]
141+
<!-- FIXME [!CODE [NVC_MFCExceptions#21](../CodeSnippet/VS_Snippets_Cpp/NVC_MFCExceptions#21)] -->
142142

143143
## <a name="cexception__reporterror"></a> CException::ReportError
144144
Call this member function to report error text in a message box to the user.
@@ -162,7 +162,7 @@ virtual int ReportError(
162162
### Example
163163
Here is an example of the use of `CException::ReportError`. For another example, see the example for [CATCH]--brokenlink--(../Topic/not%20found.md#catch).
164164

165-
[!CODE [NVC_MFCExceptions#23](../CodeSnippet/VS_Snippets_Cpp/NVC_MFCExceptions#23)]
165+
<!-- FIXME [!CODE [NVC_MFCExceptions#23](../CodeSnippet/VS_Snippets_Cpp/NVC_MFCExceptions#23)] -->
166166

167167
## See Also
168168
[CObject Class](../Topic/CObject%20Class.md)

0 commit comments

Comments
 (0)