From: Aldy Hernandez <aldyh@redhat.com>
To: tprince@computer.org
Cc: "Michael Lovett" <mlovett@morpace.com>, <gcc@gnu.org>
Subject: Re: GCC Feature question
Date: Sat, 28 Sep 2002 10:00:00 -0000 [thread overview]
Message-ID: <m33cru85va.fsf@frogsleap.quesejoda.com> (raw)
In-Reply-To: <20020928051414.076F22CD81@inet1.ywave.com>
>>>>> "Tim" == Tim Prince <tprince@computer.org> writes:
> To the extent this stuff is supported in the cygwin win32api, you may be able
> to adapt it to reconcile its conflicts with other g++ targets. You may find
> further information in the cygwin FAQ and, of course source code. It's
> certainly considered more of a library than a compiler thing.
Huh?
How are you going to do this in library code?
while (1) {
try {
if (blah)
break;
} finally {
puts("exiting loop");
}
}
next prev parent reply other threads:[~2002-09-28 16:20 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
2002-09-28 0:20 ` Tim Prince
2002-09-28 10:00 ` Aldy Hernandez [this message]
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=m33cru85va.fsf@frogsleap.quesejoda.com \
--to=aldyh@redhat.com \
--cc=gcc@gnu.org \
--cc=mlovett@morpace.com \
--cc=tprince@computer.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).