Advice needed on BIC

[Thiago Macieira]

On Wednesday, 15 de December de 2010 11:37:51 John Layt wrote:
> On Tuesday 14 December 2010 19:53:50 Alexander Neundorf wrote:
> > I'm not sure we really already care about keeping BC on Windows.
> > Windows guys: do we ?
> 
> Maybe not yet and we may be able to change stuff _now_, but once it kicks in
> on Windows we don't want to have potential timebombs waiting to go off :-)
> 
> > A private function cannot be called by anybody outside the class, it can
> > only be called from within the class, so private symbols should not make
> > it into any user of the class, so removing private functions should be
> > ok.
> 
> That was always my assumption.  Which also makes me confused as to why
> promoting from private to public would break BIC, why should any change in a
> formerly private symbol break BIC when it is essentially deleting a private
> symbol and adding a new public one?  Unless that's another MSVC 'feature'
> we're working around?

Private functions *can* be called by friends and by inline functions.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20101215/3ae0d9a1/attachment.sig>