naming convention for internal methods

[Thiago Macieira]

Aaron J. Seigo wrote:
>yeah, it's not that the Private class is declared private: (or
> protected: for that matter) that's the issue. it would mean having to
> have separate headers for them, the Private class may need to know what
> its associated object is, etc... requires a fair amount more changes to
> the existing code base that i'm not prepared to do personally right now
> =)

Ok, it isn't a problem.

As long as those methods aren't virtual, they can be cleanly removed 
later.

If they are virtual, they probably aren't internal API.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070315/7c138349/attachment.sig>