Re: How to call protected pure virtual ancestor funcs from friend function?
On 19 Mai, 15:41, "Siegfried Heintze" <siegfr...@heintze.com> wrote:
[..] What I have below works, but MS
Visual C++ 6 requires that I declare ISTACK<TYPE>::getData public! Arghhh!
Those pure virtual getData functions should be protected! How do I make
them
protected? MSVC 6 gives me syntax errors if I don't make them public! Is
this a bug in the compiler or a bug in the C++ specification?
VC6 is correct. Please look carefully at your code: Your
friend compare function is part of the STACK template,
not of the base class ISTACK. Friendship and inheritance
are independent concepts, so you cannot expect that a
friend of a derived class can access protected parts
of the its base *via a base class* instance! If the
friend would try to access getData via a STACK instance,
no such error would have occurred. 11.5/1 explains the
details of your situation.
Funnily, your compare function uses only ISTACK arguments,
so the basic question arises: Why did you not provide it
as friend function of the ISTACK template? Indeed this
would be the most reasonable decision.
Since you provided source code, here are some further
points:
- The "abstract" base class misses a virtual d'tor.
- The source code as is does not compile, because the
compare functions uses several unavailable members of
ISTACK. If you want any serious answers to your question,
your snippet should be complete and should also not have
unnecessary members (e.g. missing: len,state in STACK;
getLength() in ISTACK).
- It's quite unusual to use full UPPERCASE letter names
for any non-macro entity in C/C++.
Is there a fix other than declaring them public and violating the fundemental concept of a
stack? I tried implementing compare as a member function but then it could
not access the private or protected parts of the stack that is an argument
to the compare member function. Is that conistent with the C++ spec?
Move compare into the ISTACK template, as explained above.
You also could have made compare a normal member function
of ISTACK (and not STACK), because every member has
access to the protected and private parts of its class,
see 11/1, 2nd bullet:
"- protected; that is, its name can be used only by members
and friends of the class in which it is declared, and by
members and friends of classes derived from this class (see 11.5)."
Personally I would prefer the non-member friend function
here, because of it's argument symmetry.
Greetings from Bremen,
Daniel Kr?gler
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]