[Qgis-developer] protected members to be considered API ?
Sandro Santilli
strk at keybit.net
Wed Jan 27 08:04:22 PST 2016
On Wed, Jan 27, 2016 at 04:51:07PM +0100, Matthias Kuhn wrote:
>
>
> On 01/27/2016 04:34 PM, Sandro Santilli wrote:
> > On Wed, Jan 27, 2016 at 10:04:20AM +0100, Sandro Santilli wrote:
> >> On Wed, Jan 27, 2016 at 09:49:48AM +0100, Matthias Kuhn wrote:
> >>> Anything not LIB_EXPORTed (or private) should be considered an
> >>> implementation detail,
> >> What about protected members ?
> > For example:
> >
> > class CORE_EXPORT QgsFeatureRendererV2
> >
> > protected static const unsigned char* _getPoint(
> > QPointF& pt, QgsRenderContext& context,
> > const unsigned char* wkb // <-- no boundary info !
> > );
> I'd not treat protected different from public, both are accessible for
> external code.
Ok.
> If it's possible to keep the old API in place and have it deprecated, it
> is preferable.
I'm taking this path.
--strk;
More information about the Qgis-developer
mailing list