public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Branko Čibej" <brane@xbc.nu>
To: "Andrew V. Fionik" <fionika@papillon.ru>
Cc: gcc@gcc.gnu.org
Subject: Re: I want try...finally
Date: Thu, 15 May 2003 19:06:00 -0000	[thread overview]
Message-ID: <3EC3E550.3010203@xbc.nu> (raw)
In-Reply-To: <000001c31afb$2dcc40e0$fc15a8c0@timberwolf>

Andrew V. Fionik wrote:

>Hi, guys.
>
>I think that you doing great job by making GCC and G++. However i feel that
>C++
>compiler lacks support for one great language construct "try...finally". I'm
>sure you know about it. It widely used in prooperitary Microsoft and Borland
>C++/Delphi compilers. This construct allows to easy write safe, elegant, and
>well readably code.
>
Anything that can be done with try...finally can also be done with
destructors without extending the language.


-- 
Brane ÄŒibej   <brane@xbc.nu>   http://www.xbc.nu/brane/

      parent reply	other threads:[~2003-05-15 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 16:02 Andrew V. Fionik
2003-05-15 16:41 ` Matt Austern
2003-05-15 19:06 ` Branko Čibej [this message]

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=3EC3E550.3010203@xbc.nu \
    --to=brane@xbc.nu \
    --cc=fionika@papillon.ru \
    --cc=gcc@gcc.gnu.org \
    /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).