Subject: Re: [boost] [xint] Design Question
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-06-17 06:57:17
Chad Nelson wrote:
> On 06/17/2010 01:16 AM, Jeffrey Lee Hellrung, Jr. wrote:
> >> [...] But I don't understand why it failed in the first place.
> >> [...] Why aren't they visible without the base class name from
> >> *within* the combined class?
> > In short: Your base classes are dependent types, so using
> > anything from them (functions, types, templates, etc.) will
> > have to be explicitly qualified (as you've discovered) or
> > brought into the derived class' scope with a using
> > declaration.
> > http://womble.decadentplace.org.uk/c++/template-faq.html#base-lookup
> I can't tell from that page, but I assume that using the "standard"
> method (i.e. specifying the full base class name before the function
> name) will work on what that page calls "intermediate" and "CFront"
> compilers as well? In other words, does anyone here know of any
> compatibility problems caused by that, or by a "using" directive in
> the class to do the same thing?
I don't think either would cause a problem, but it is typical to reference policy class member functions using scope resolution. That even permits the policies to use the same function names, though it is generally good to avoid that.
Rob Stewart robert.stewart_at_[hidden]
Software Engineer, Core Software using std::disclaimer;
Susquehanna International Group, LLP http://www.sig.com
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.