Skip to content
Merged
Changes from all commits
Commits
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
8 changes: 4 additions & 4 deletions docs/text/using-tchar-h-data-types-with-mbcs-code.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ When the manifest constant `_MBCS` is defined, a given generic-text routine maps

Following are three solutions for preventing this type conflict (and the C compiler warnings or C++ compiler errors that would result):

- Use the default behavior. Tchar.h provides generic-text routine prototypes for routines in the run-time libraries, as in the following example.
- Use the default behavior. tchar.h provides generic-text routine prototypes for routines in the run-time libraries, as in the following example.

```cpp
char * _tcsrev(char *);
Expand All @@ -29,7 +29,7 @@ Following are three solutions for preventing this type conflict (and the C compi
#define _USE_INLINING
```

This method causes an inline function thunk, provided in Tchar.h, to map the generic-text routine directly to the appropriate MBCS routine. The following code excerpt from Tchar.h provides an example of how this is done.
This method causes an inline function thunk, provided in tchar.h, to map the generic-text routine directly to the appropriate MBCS routine. The following code excerpt from tchar.h provides an example of how this is done.

```cpp
__inline char *_tcsrev(char *_s1)
Expand All @@ -44,7 +44,7 @@ Following are three solutions for preventing this type conflict (and the C compi
#define _MB_MAP_DIRECT
```

This approach provides a fast alternative if you do not want to use the default behavior or cannot use inlining. It causes the generic-text routine to be mapped by a macro directly to the MBCS version of the routine, as in the following example from Tchar.h.
This approach provides a fast alternative if you do not want to use the default behavior or cannot use inlining. It causes the generic-text routine to be mapped by a macro directly to the MBCS version of the routine, as in the following example from tchar.h.

```cpp
#define _tcschr _mbschr
Expand All @@ -54,4 +54,4 @@ Following are three solutions for preventing this type conflict (and the C compi

## See Also

[Generic-Text Mappings in Tchar.h](../text/generic-text-mappings-in-tchar-h.md)
[Generic-Text Mappings in tchar.h](../text/generic-text-mappings-in-tchar-h.md)