On Thu May 22 2008 10:49:25 Jordi Gutiérrez Hermoso wrote: > You keep talking about scope. The access specifier should affect scope > and name resolution? This does not make sense! The public function is > available, a using declaration should bring that function from A's > scope into B's scope, but the compiler tries to resolve the call > "b.f(a)" call to the inaccessible private function anyways.
No it doesn't. The error message, which you keep failing to post, would be for the line of the "using", indicating that you're attempting to "using" a private function. This is not the same as trying "to resolve the call". You are creating a permanent record of your very uninformed status, and teaching you basic C++ programming is off-topic for this list. Please stop. Go study the issue. If you have questions post them to a C++ list. --Mike Bird -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
