public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: paolo@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, morandini@aero.polimi.it, nobody@gcc.gnu.org Subject: Re: libstdc++/6671: ext search path Date: Sun, 19 May 2002 08:48:00 -0000 [thread overview] Message-ID: <20020519154830.20670.qmail@sources.redhat.com> (raw) Synopsis: ext search path State-Changed-From-To: open->analyzed State-Changed-By: paolo State-Changed-When: Sun May 19 08:48:29 2002 State-Changed-Why: Hi. I see two issues here: 1- If all is needed is a shorter access to the old STL extensions (those exisiting in ext when the doc you mention was written, i.e., hash_map, hash_set, rope, slist) then the solution is simply using -idirafter instead of -I (see libstdc++/6720). This allows to write safely <hash_map> (and still <iostream>, of course, as in your testcase). 2- OTOH, in this case <ext/memory>, f.i., must still be written in full in order to disambiguate it from <memory>. In order to solve the latter problem, the only solution I see is renaming the new extension bits to something different. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6671
next reply other threads:[~2002-05-19 15:48 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-19 8:48 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-20 14:19 paolo 2002-05-16 1:06 morandini
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=20020519154830.20670.qmail@sources.redhat.com \ --to=paolo@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=morandini@aero.polimi.it \ --cc=nobody@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: linkBe 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).