Re: name binding from one template to another

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Wed, 12 Mar 2008 22:49:18 -0400

Message-ID:

<eGoqJVLhIHA.4396@TK2MSFTNGP04.phx.gbl>

"George" <George@discussions.microsoft.com> wrote in message
news:C1DCE0DD-47FF-4E7E-B563-51E0988E3790@microsoft.com

A dependent name is one that refers to, or otherwise depends on, the
_internals_ of a parameterized type (e.g. its members or its
associated namespaces). With such names, you can't even figure out
_which_ declaration the name refers to, let alone the type of the
referred-to entity, until the template is instantiated and the
parameterized type becomes concrete.

I want to complement your definition of dependent name. Not only the
internals of a parameterized type, but also the type itself.

That's incorrect, however much you might want it to be so.

For example,

template <class T> void func (T a)
{
   vector<T> vc;
   T tmp = a;
   vc.push_back (a);

   return;
}

In the above code, a, tmp are dependent names and vc is not dependent
name.

None of these are dependent names. The only dependent name in this code
is push_back.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925