From: Corey Kosak <kosak@cs.cmu.edu>
To: egcs@cygnus.com
Cc: Greg Galloway <gregg@eoeml.gtri.gatech.edu>
Subject: Re: C++ and DEC Unix: string too long
Date: Tue, 28 Oct 1997 15:21:00 -0000 [thread overview]
Message-ID: <199710282321.PAA08249@cygnus.com> (raw)
> Has anyone got EGCS/C++ to work on an Alpha under DEC Unix 3.2?
> I get an error about string too long because the mangled name of
> a template instantiation (hash_map in this case) is 4144 chars
> long.
Amazing that it's the 90's and some people [DEC] still write software with
arbitrary fixed limits. "Surely no one would ever want a symbol longer than
4K characters."
The standard workaround, as far as I know, is to subclass string, something
like
class mystring : public string {
...
};
`mystring' needs to have constructor stubs for all the constructors in
`string', plus probably stubs for the overloaded operators as well.
next reply other threads:[~1997-10-28 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-28 15:21 Corey Kosak [this message]
1997-10-28 19:48 ` Joe Buck
-- strict thread matches above, loose matches on Subject: below --
1997-10-28 12:21 Greg Galloway
1997-10-28 17:57 ` dave madden
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=199710282321.PAA08249@cygnus.com \
--to=kosak@cs.cmu.edu \
--cc=egcs@cygnus.com \
--cc=gregg@eoeml.gtri.gatech.edu \
/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).