From: Kim Minh Kaplan <kimminh.kaplan+nomuch@afnic.fr>
To: Vladimir Marek <vlmarek@volny.cz>
Cc: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] don't store temporary value returned from c_str()
Date: Tue, 30 Apr 2013 09:44:01 +0000 [thread overview]
Message-ID: <87ehdsfj4u.fsf@kaki.tech.prive.nic.fr> (raw)
In-Reply-To: <20130430084852.GA19599@pub.cz.oracle.com> (Vladimir Marek's message of "Tue, 30 Apr 2013 10:48:52 +0200")
Vladimir Marek :
> Thank you, I found it eventually too. But I wrote little test program
> (attached) which confused me. I haven't had much time to take a look
> into it since weekend.
>
> The idea is to have temporary object where I can detect whether
> destructor was called.
>
> I thought that
>
> printf ("%s\n", s.c_str());
> will print "test"
>
> and
>
> x=s.c_str();
> printf ("%s\n", x);
>
> will print "destroyed"
>
> On my machine both prints "destroyed".
You have to somehow instantiate a temporary object, using a function
call for example.
#include <string.h>
#include <stdio.h>
struct example {
char data[10];
char *c_str() { return data; }
example() { strcpy(data, "test"); }
~example() { strcpy(data, "destroyed"); }
};
example foo()
{
example res;
return res;
}
main()
{
printf("%s\n", foo().c_str());
char *x = foo().c_str();
printf("%s\n", x);
}
Kim Minh.
next prev parent reply other threads:[~2013-04-30 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 21:12 [PATCH] don't store temporary value returned from c_str() Vladimir.Marek
2013-04-27 9:33 ` Tomi Ollila
2013-04-27 10:11 ` Vladimir Marek
2013-04-27 11:53 ` David Bremner
2013-04-27 15:59 ` Vladimir Marek
2013-04-30 6:12 ` Kim Minh Kaplan
2013-04-30 8:48 ` Vladimir Marek
2013-04-30 9:44 ` Kim Minh Kaplan [this message]
2013-05-01 11:28 ` Vladimir Marek
2013-04-27 12:30 ` Jani Nikula
2013-04-27 13:22 ` Tomi Ollila
2013-04-27 16:05 ` Vladimir Marek
2013-04-29 21:23 ` David Bremner
2013-05-01 21:33 ` Vladimir Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehdsfj4u.fsf@kaki.tech.prive.nic.fr \
--to=kimminh.kaplan+nomuch@afnic.fr \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
--cc=vlmarek@volny.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).