From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: Allow C++ or C99 in sim/*?
Date: Tue, 05 Aug 2003 04:27:00 -0000 [thread overview]
Message-ID: <20030805042727.GA13980@nevyn.them.org> (raw)
In-Reply-To: <3F2F31B6.3060900@redhat.com>
On Tue, Aug 05, 2003 at 12:25:26AM -0400, Andrew Cagney wrote:
> Two parts, and two features, come to mind:
>
> - the sim-endian code which, I think, would work better using templates
>
> - the h/w devices which are objects with virtual methods
>
> I suspect a careful choice of language features will avoid the
> performance problems - no multiple inheritance for instance.
>
> after that, well who knows.
At which point, it seems, you're redesigning sid rather than sim?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-05 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 0:16 Andrew Cagney
2003-08-02 0:43 ` Daniel Jacobowitz
2003-08-02 0:47 ` David Carlton
[not found] ` <mailpost.1059783391.21631@news-sj1-1>
2003-08-02 1:30 ` cgd
2003-08-05 4:25 ` Andrew Cagney
2003-08-05 4:27 ` Daniel Jacobowitz [this message]
2003-08-02 1:11 Michael Elizabeth Chastain
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=20030805042727.GA13980@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.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).