From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Remove a cleanup from scm-frame.c
Date: Sun, 22 Apr 2018 23:47:00 -0000 [thread overview]
Message-ID: <87a7tug5xj.fsf@tromey.com> (raw)
In-Reply-To: <43a02241b2a0b1178a6dd8dfbd2ad581@polymtl.ca> (Simon Marchi's message of "Sun, 22 Apr 2018 10:21:49 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
Simon> This looks good to me at first glance. Do you know if scm exceptions
Simon> (scm_throw) play well with C++, the destructors of the objects in the
Simon> exited scopes will correctly be called?
I don't believe so, which is why this patch introduces a new scope.
Tom
next prev parent reply other threads:[~2018-04-22 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 22:39 Tom Tromey
2018-04-22 14:21 ` Simon Marchi
2018-04-22 23:47 ` Tom Tromey [this message]
2018-04-23 1:40 Simon Marchi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7tug5xj.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox