<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - NetworkSession: switch to use subclasses for NetworkSession and NetworkDataTask implementations"
href="https://bugs.webkit.org/show_bug.cgi?id=163777#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - NetworkSession: switch to use subclasses for NetworkSession and NetworkDataTask implementations"
href="https://bugs.webkit.org/show_bug.cgi?id=163777">bug 163777</a>
from <span class="vcard"><a class="email" href="mailto:krollin@apple.com" title="Keith Rollin <krollin@apple.com>"> <span class="fn">Keith Rollin</span></a>
</span></b>
<pre><span class="quote">> I think these overrides should remain private.</span >
I'm curious about your desire for this. This is an idiom that I've not seen used before. It seems to me that it could be problematic (for instance, the actual compilation problem I encountered). Others seem to feel the same way: <<a href="http://stackoverflow.com/questions/484592/overriding-public-virtual-functions-with-private-functions-in-c">http://stackoverflow.com/questions/484592/overriding-public-virtual-functions-with-private-functions-in-c</a>>. That article (in part) refers to <<a href="https://isocpp.org/wiki/faq/proper-inheritance#hiding-inherited-public">https://isocpp.org/wiki/faq/proper-inheritance#hiding-inherited-public</a>>.
So how do you come down on the opposite side of these opinions? What's being communicated by making public methods private in the derived class?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>