From: Jason Merrill <jason@redhat.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: "Michael Lovett" <mlovett@morpace.com>, <gcc@gnu.org>
Subject: Re: GCC Feature question
Date: Fri, 04 Oct 2002 12:26:00 -0000 [thread overview]
Message-ID: <wvlvg4m9idt.fsf@prospero.cambridge.redhat.com> (raw)
In-Reply-To: <m37kh693un.fsf@frogsleap.quesejoda.com> (Aldy Hernandez's message of "27 Sep 2002 20:42:56 -0700")
On 27 Sep 2002 20:42:56 -0700, Aldy Hernandez <aldyh@redhat.com> wrote:
> > We are porting apps to UNIX from Windows but so far can't find a
> > compiler with try/finally. It is such a useful, convenient construct
> > it is hard to imagine structured programming without it.
>
> C or C++? With C++ you can emulate it with constructors, albeit ugly.
It's not *that* ugly. For C++ using a destructor encourages you to write
reusable finalization code.
Jason
next prev parent reply other threads:[~2002-10-04 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 22:15 Michael Lovett
2002-09-27 22:45 ` Aldy Hernandez
2002-10-04 12:26 ` Jason Merrill [this message]
2002-09-28 0:20 ` Tim Prince
2002-09-28 10:00 ` Aldy Hernandez
2002-10-04 12:52 Michael Lovett
[not found] <sd9dae8d.087@farm_groupwise1_srv.morpace-i.com>
2002-10-04 15:20 ` Jason Merrill
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=wvlvg4m9idt.fsf@prospero.cambridge.redhat.com \
--to=jason@redhat.com \
--cc=aldyh@redhat.com \
--cc=gcc@gnu.org \
--cc=mlovett@morpace.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).