Question

In Route-Me from MapBox I’ve seen iVars implemented like this:

@implementation RMMapView
{
    BOOL _delegateHasBeforeMapMove;
    BOOL _delegateHasAfterMapMove;
    BOOL _delegateHasBeforeMapZoom;
    BOOL _delegateHasAfterMapZoom;
    BOOL _delegateHasMapViewRegionDidChange;
    BOOL _delegateHasDoubleTapOnMap;
    BOOL _delegateHasSingleTapOnMap;
    BOOL _delegateHasSingleTapTwoFingersOnMap;
    BOOL _delegateHasLongSingleTapOnMap;
    BOOL _delegateHasTapOnAnnotation;
    BOOL _delegateHasDoubleTapOnAnnotation;
    BOOL _delegateHasTapOnLabelForAnnotation;
    BOOL _delegateHasDoubleTapOnLabelForAnnotation;
    BOOL _delegateHasShouldDragMarker;
    BOOL _delegateHasDidDragMarker;
    BOOL _delegateHasDidEndDragMarker;
    BOOL _delegateHasLayerForAnnotation;
    BOOL _delegateHasWillHideLayerForAnnotation;
    BOOL _delegateHasDidHideLayerForAnnotation;

    BOOL _constrainMovement;
    RMProjectedRect _constrainingProjectedBounds;

    float _lastZoom;
    CGPoint _lastContentOffset, _accumulatedDelta;
    BOOL _mapScrollViewIsZooming;
}

That is, it’s declared in the .m files instead of the .h files.
If I sub-class this RMMapView, I don’t see these iVars. Is there a way to make it visible in subclass while not to the world?

It’s my intention to preserve the original code so chose to sub-class and modify the behavior from there. But perhaps just change the files directly and update codes from the main repostory via git is a better way to do it?

Answer 1

In Objective-C (as in other OO languages) most developers consider instance variables an implementation detail of the defining class. They should not be accessed directly by other classes.

In this case the instance variables are declared in the implementation which is a strong hint that the authors of RMMapView don’t want to expose the variables to outside code.