Is this a bug?

[freeagle]

freeagle wrote:
> Tom S wrote:
>> freeagle wrote:
>>> the problem is not that i have to type a bit more to actually call 
>>> the method, i just don't understand why its not part of Win32Window 
>>> interface, when Win32Window class is publicly derived from BaseWindow 
>>> defining public method Dimension2D size();
>>
>> That may be because of the symbol resolution method that is currently 
>> being attacked in various posts. In that one example of yours, the 
>> compiler figures out that you want a 'size' function of the 
>> Win32Window, it checks it and cant see the right version. It doesnt 
>> check the base class because of how the method resolution works. 
>> Weird, yeah :P
>>
>>
> 
> well yeah, this way, you have to show whole inheritance tree to the user 
> of the lib so he can use it. I think this damages encapsulation. I dont 
> want the user to know there is a BaseWindow class, i want him to be 
> happy just with a knowledge of Win32Window class.

ok, you dont, im taking back my last statements ;) thanks guys for the help