public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Love-Jensen <eljay@adobe.com>
To: Ajay Bansal <Ajay_Bansal@infosys.com>, <gcc-help@gcc.gnu.org>
Subject: Re: no matching function for call to ``vector<C1,allocator<C1>>::at (int &) const'
Date: Thu, 23 Jan 2003 13:27:00 -0000	[thread overview]
Message-ID: <BA554893.6EA9%eljay@adobe.com> (raw)
In-Reply-To: <2B721C6525F0D411B1E900B0D0226BDD02148C0A@mohmsg01.ad.infosys.com>

Hi Ajay,

You can check out which header files are introduced into your source code
via:

g++ -M foo.cpp > foo.d

...and take a critical look at foo.d.  It will tell you which header files,
in particular compiler header files, are being pulled in.

Are those header files the ones from the old 2.10 or 2.90 Standard Library,
or are they the ones from the 3.x Standard Library?  (The Standard Library
has it's own version, independent of the GCC release.)

If you are unsure, you might want to open the vector header file (i.e.,
stl_vector.h has the implementation) and confirm that it has an at() method.

--Eljay

  reply	other threads:[~2003-01-23 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 13:20 Ajay Bansal
2003-01-23 13:27 ` John Love-Jensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-23 18:12 no matching function for call to``vector<C1,allocator<C1>>::at " Ajay Bansal
2003-01-23 13:13 no matching function for call to ``vector<C1, allocator<C1>>::at " Ajay Bansal
2003-01-23 13:18 ` John Love-Jensen
2003-01-23 12:52 no matching function for call to ``vector<C1, allocator<C1> >::at " Ajay Bansal
2003-01-23 13:11 ` John Love-Jensen

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=BA554893.6EA9%eljay@adobe.com \
    --to=eljay@adobe.com \
    --cc=Ajay_Bansal@infosys.com \
    --cc=gcc-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).