From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Nicolas Roard <nicolas@roard.com>
Cc: Gregory John Casamento <greg_casamento@yahoo.com>,
Lars Sonchocky-Helldorf <lars.sonchocky-helldorf@hamburg.de>,
Mike Stump <mrs@apple.com>,
gcc@gcc.gnu.org, discuss-gnustep@gnu.org
Subject: Re: Is ObjC++ still in time for 4.0?
Date: Wed, 17 Nov 2004 23:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0411172312100.24951@digraph.polyomino.org.uk> (raw)
In-Reply-To: <9F62E546-38EB-11D9-B4B5-0003934632AA@roard.com>
On Wed, 17 Nov 2004, Nicolas Roard wrote:
> And now it seems that the problems are becoming more political than technical
> ??
The problems are technical.
It is for the ObjC++ maintainers to produce patches that do not adversely
affect the memory consumption, compile time performance or maintainability
of the C or C++ front ends. These are technical issues. If existing
slots in datastructures are to be reused, then all uses of those
datastructures in the existing front ends need analysing to make sure this
is safe (probably with checking added to the accessors to ensure it
remains safe). If new slots are added, statistics of performance on real
code are needed to show no statistically significant adverse effect.
Similarly, if conditionals are added anywhere someone thinks might be a
hot spot, profiling results are needed to show there is no performance
impact.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
next prev parent reply other threads:[~2004-11-17 23:17 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
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 [this message]
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=Pine.LNX.4.61.0411172312100.24951@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=discuss-gnustep@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=greg_casamento@yahoo.com \
--cc=lars.sonchocky-helldorf@hamburg.de \
--cc=mrs@apple.com \
--cc=nicolas@roard.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).