public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lars Sonchocky-Helldorf <lars.sonchocky-helldorf@hamburg.de>
To: Mike Stump <mrs@apple.com>
Cc: gcc@gcc.gnu.org, discuss-gnustep@gnu.org
Subject: Re: Is ObjC++ still in time for 4.0?
Date: Wed, 17 Nov 2004 21:53:00 -0000	[thread overview]
Message-ID: <93CA0604-38E1-11D9-9815-0030654C2998@hamburg.de> (raw)
In-Reply-To: <C949FF38-2681-48A5-94D9-0228551C5902@apple.com>


Am Mittwoch, 17.11.04 um 21:26 Uhr schrieb Mike Stump:

> On Nov 17, 2004, at 1:58 AM, Lars Sonchocky-Helldorf wrote:
>> I wanted to ask what the current status of Objective-C++ for mainline 
>> gcc is. While there have been a lot of activity on the gcc-patches 
>> and gcc-cvs lists several month ago it is now relatively silent 
>> regarding this topic. Is all the work done now or did the release 
>> plan slip backwards (to 4.1 or whatever)?
>
> Last I knew, everything was solidly wedged behind Geoff's objection 
> with no plan forward.  The objection will either have to be withdrawn, 
> or Geoff will have to communicate his vision before any progress can 
> be made.

What kind of objection was that? (you can give me a pointer to the 
archived mail at http://gcc.gnu.org/ml/gcc/ or so)

Would it be possible to ask Geoff to get down to business?

>
> I think this should be resolved now, as as we push it forward, it will 
> pass the drop dead date, and objective-c++ will have to be jettisoned 
> from gcc 4.0.0.  :-(
>
> Mark, I suppose we can discuss when that drop dead date is.  Has it 
> already passed?

Hopefully not!

>
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnustep
>

  reply	other threads:[~2004-11-17 21:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 10:28 Lars Sonchocky-Helldorf
2004-11-17 20:51 ` Mike Stump
2004-11-17 21:53   ` Lars Sonchocky-Helldorf [this message]
2004-11-17 22:28     ` Ziemowit Laski
2004-11-17 22:54     ` Gregory John Casamento
2004-11-17 23:02       ` Nicolas Roard
2004-11-17 23:31         ` Joseph S. Myers
2004-11-17 23:17       ` Phil Edwards
2004-11-17 23:50         ` Alex Perez
2004-11-18  0:06           ` Joe Buck
2004-11-18  0:35         ` Gregory John Casamento
2004-11-18  0:46           ` Gregory John Casamento
2004-11-18  0:53   ` Mark Mitchell
2004-11-18  1:18     ` Giovanni Bajo
2004-11-18 23:22   ` Geoffrey Keating
2004-11-18 23:28     ` Gregory John Casamento
2004-11-19  0:57     ` Ziemowit Laski
2004-11-19  1:26       ` Rogelio Serrano
2004-11-19  1:41       ` Helge Hess
2004-11-19  4:26         ` Gregory John Casamento
2004-11-19  5:49         ` Matt Austern
2004-11-19  6:42           ` Ziemowit Laski
2004-11-19  7:52             ` Phil Edwards
2004-11-22  3:22               ` Chuck Robey
2004-11-22 10:07                 ` Phil Edwards
2004-11-22 10:31                 ` Ranjit Mathew
2004-11-19 19:44           ` Dale Johannesen
2004-11-19 20:04             ` Dan Grillo
2004-11-19 20:08             ` Dave Korn
2004-11-19 13:31 Richard Kenner
2004-11-19 20:22 ` Ziemowit Laski

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=93CA0604-38E1-11D9-9815-0030654C2998@hamburg.de \
    --to=lars.sonchocky-helldorf@hamburg.de \
    --cc=discuss-gnustep@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mrs@apple.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).