From: shamino1@usa.net (David C.)
To: help-gcc@gnu.org
Subject: Re: Linking problems, mangling ?
Date: Fri, 17 Dec 1999 11:52:00 -0000 [thread overview]
Message-ID: <ur9glpcyt.fsf@qqqq.invalid> (raw)
In-Reply-To: <83b4kc$hdt$1@news.stna.dgac.fr>
hamon@timide.stna.dgac.fr. (Roland TTK) writes:
>
> Or maybe I could find another implementation of the STL ??
Have you checked to see if you can get an updated compiler from Sun?
Their "Visual Workshop C++" package
( http://www.sun.com/workshop/visual/spec.html ) claims to be ISO
compilant, which means it should have STL support.
I suggest downloading a 30-day trial version (from Sun's web site) to
see if it's compatible with the library you want to use. If it is, then
you may want to consider purchasing one or more licenses.
Unless/until your library vendor releases a gcc version, I don't think
you many other choices. (If you're not using too much of the STL, you
might be able to write some quick-and-dirty implementations of the
templates you need, but that may end up being more work than it's
worth.)
-- David
WARNING: multiple messages have this Message-ID
From: shamino1@usa.net (David C.)
To: help-gcc@gnu.org
Subject: Re: Linking problems, mangling ?
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <ur9glpcyt.fsf@qqqq.invalid> (raw)
Message-ID: <19991231222400.rCZBkUKNbAJn1IHCDIMkpMdjrbX4xExDkKjiGTe-eXU@z> (raw)
In-Reply-To: <83b4kc$hdt$1@news.stna.dgac.fr>
hamon@timide.stna.dgac.fr. (Roland TTK) writes:
>
> Or maybe I could find another implementation of the STL ??
Have you checked to see if you can get an updated compiler from Sun?
Their "Visual Workshop C++" package
( http://www.sun.com/workshop/visual/spec.html ) claims to be ISO
compilant, which means it should have STL support.
I suggest downloading a 30-day trial version (from Sun's web site) to
see if it's compatible with the library you want to use. If it is, then
you may want to consider purchasing one or more licenses.
Unless/until your library vendor releases a gcc version, I don't think
you many other choices. (If you're not using too much of the STL, you
might be able to write some quick-and-dirty implementations of the
templates you need, but that may end up being more work than it's
worth.)
-- David
next prev parent reply other threads:[~1999-12-17 11:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-16 6:36 Roland TTK
1999-12-16 7:23 ` Eric Meijer
1999-12-16 8:58 ` Roland TTK
1999-12-16 11:57 ` Dave Sieber
1999-12-31 22:24 ` Dave Sieber
1999-12-17 11:52 ` David C. [this message]
1999-12-31 22:24 ` David C.
1999-12-31 22:24 ` Roland TTK
1999-12-16 11:06 ` Mike Albaugh
1999-12-31 22:24 ` Mike Albaugh
1999-12-31 22:24 ` Eric Meijer
1999-12-31 22:24 ` Roland TTK
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=ur9glpcyt.fsf@qqqq.invalid \
--to=shamino1@usa.net \
--cc=help-gcc@gnu.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).