From: Jonathan Larmour <jlarmour@redhat.com>
To: Ho Shui Choy Stanley PS03B NCS <scho@ncs.com.sg>,
eCos discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Vector support for eCos
Date: Tue, 17 Apr 2001 18:13:00 -0000 [thread overview]
Message-ID: <3ADCEA45.8B453047@redhat.com> (raw)
In-Reply-To: <19C34CD863B1D4118E2800508BAF663A0112F608@STONE>
Ho Shui Choy Stanley PS03B NCS wrote:
>
> I'm refering to the vector in the standard template library
Ah you mean C++ vectors. Porting STL should not be very difficult, but we
don't have full libstdc++ support in eCos as yet.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next parent reply other threads:[~2001-04-17 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19C34CD863B1D4118E2800508BAF663A0112F608@STONE>
2001-04-17 18:13 ` Jonathan Larmour [this message]
2001-04-17 18:48 ` Rosimildo da Silva
2001-04-18 8:55 ` Jonathan Larmour
2001-04-18 11:04 Rosimildo daSilva
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 2:05 Ho Shui Choy Stanley PS03B NCS
2001-04-17 6:53 ` Jonathan Larmour
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=3ADCEA45.8B453047@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=scho@ncs.com.sg \
/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).