提交 5c065f85 编写于 作者: H Hyuk Myeong 提交者: Herb Sutter

Fix typos (#1549)

* R.37 : it callees -> its callees
* ES.65 : a different part from the original paper
上级 c68a3958
......@@ -9851,7 +9851,7 @@ The following should not pass code review:
void my_code()
{
// BAD: passing pointer or reference obtained from a nonlocal smart pointer
// that could be inadvertently reset somewhere inside f or it callees
// that could be inadvertently reset somewhere inside f or its callees
f(*g_p);
// BAD: same reason, just passing it as a "this" pointer
......@@ -12315,7 +12315,7 @@ wrong results, or memory corruption.
This rule is an obvious and well-known language rule, but can be hard to follow.
It takes good coding style, library support, and static analysis to eliminate violations without major overhead.
This is a major part of the discussion of [C++'s resource- and type-safety model](#Stroustrup15).
This is a major part of the discussion of [C++'s model for type- and resource-safety](#Stroustrup15).
**See also**:
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册