Skip to content

Commit f04dadc

Browse files
committed
Insert 'the'
1 parent 0b1ec2c commit f04dadc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

manual.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -306,7 +306,7 @@ If you want to completely disable memory leak detection then you can do so by bu
306306

307307
### Conflicts with operator new macros (STL!)
308308

309-
It is common for the memory leak detection macros to conflict with an overloaded operator new or with STL. This is because the macro replaces the call to operator new to a call to operator new with __FILE__, and __LINE__. If you overload operator new, it will replace your overloaded definition resulting in a compiler error. This is common when using Standard C++ library (STL).
309+
It is common for the memory leak detection macros to conflict with an overloaded operator new or with STL. This is because the macro replaces the call to operator new to a call to operator new with __FILE__, and __LINE__. If you overload operator new, it will replace your overloaded definition resulting in a compiler error. This is common when using the Standard C++ library (STL).
310310

311311
#### Resolving conflicts with STL
312312
The easiest way is not to pass the --include MemoryLeakDetectionNewMacros.h to the compiler, but this would lose all your file and line information. So this is not recommended. An alternative is to create your own NewMacros.h file which will include the STL file *before* the new macro is defined. For example, the following NewMacros file can be used for a program that uses std::list:

0 commit comments

Comments
 (0)