📄 temporaries.html
字号:
<html lang="en">
<head>
<title>Using the GNU Compiler Collection (GCC)</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Using the GNU Compiler Collection (GCC)">
<meta name="generator" content="makeinfo 4.3">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home">
<!--
Copyright © 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
<p>Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with the
Invariant Sections being "GNU General Public License" and "Funding
Free Software", the Front-Cover texts being (a) (see below), and with
the Back-Cover Texts being (b) (see below). A copy of the license is
included in the section entitled "GNU Free Documentation License".
<p>(a) The FSF's Front-Cover Text is:
<p>A GNU Manual
<p>(b) The FSF's Back-Cover Text is:
<p>You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
funds for GNU development.-->
</head>
<body>
<div class="node">
<p>
Node:<a name="Temporaries">Temporaries</a>,
Next:<a rel="next" accesskey="n" href="Copy-Assignment.html#Copy%20Assignment">Copy Assignment</a>,
Previous:<a rel="previous" accesskey="p" href="Static-Definitions.html#Static%20Definitions">Static Definitions</a>,
Up:<a rel="up" accesskey="u" href="C---Misunderstandings.html#C++%20Misunderstandings">C++ Misunderstandings</a>
<hr><br>
</div>
<h4 class="subsection">Temporaries May Vanish Before You Expect</h4>
<p>It is dangerous to use pointers or references to <em>portions</em> of a
temporary object. The compiler may very well delete the object before
you expect it to, leaving a pointer to garbage. The most common place
where this problem crops up is in classes like string classes,
especially ones that define a conversion function to type <code>char *</code>
or <code>const char *</code>--which is one reason why the standard
<code>string</code> class requires you to call the <code>c_str</code> member
function. However, any class that returns a pointer to some internal
structure is potentially subject to this problem.
<p>For example, a program may use a function <code>strfunc</code> that returns
<code>string</code> objects, and another function <code>charfunc</code> that
operates on pointers to <code>char</code>:
<pre class="example"> string strfunc ();
void charfunc (const char *);
void
f ()
{
const char *p = strfunc().c_str();
...
charfunc (p);
...
charfunc (p);
}
</pre>
<p>In this situation, it may seem reasonable to save a pointer to the C
string returned by the <code>c_str</code> member function and use that rather
than call <code>c_str</code> repeatedly. However, the temporary string
created by the call to <code>strfunc</code> is destroyed after <code>p</code> is
initialized, at which point <code>p</code> is left pointing to freed memory.
<p>Code like this may run successfully under some other compilers,
particularly obsolete cfront-based compilers that delete temporaries
along with normal local variables. However, the GNU C++ behavior is
standard-conforming, so if your program depends on late destruction of
temporaries it is not portable.
<p>The safe way to write such code is to give the temporary a name, which
forces it to remain until the end of the scope of the name. For
example:
<pre class="example"> string& tmp = strfunc ();
charfunc (tmp.c_str ());
</pre>
</body></html>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -