springox / anlock Goto Github PK

1.What's the exact difference between ANReadWriteLock & ANRecursiveRWLock
We could c the difference in performance but what's the exact difference in usage? And what's the former cannot do but the latter can especially?

2.We can take advantage of a handful of example code 2 test if an interface which implements NSCoding protocol do satisfy the recursive lock.

//    NSRecursiveLock *lock = [[NSRecursiveLock alloc] init];
    ANRecursiveRWLock *lock = [[ANRecursiveRWLock alloc] init];

    dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), ^{

        static void (^RecursiveMethod)(int);

        RecursiveMethod = ^(int value) {

            [lock lock];
            if (value > 0) {

                NSLog(@"value = %d", value);
                sleep(2);
                RecursiveMethod(value - 1);
            }
            [lock unlock];
        };

        RecursiveMethod(5);
    });

If u employ the ANRecursiveRWLock instead of NSRecursiveLock which comes from OC, u'd be aware of that it's gonna be deadlocked.
As we all no, a write operation cannot b disturbed by a read operation as the logic in the code.
But could u declare what's the meaning of recursive lock on earth?
3Q in advance~

@property (atomic, assign) int atomicFlag;

//Atomic Flag
timeBefore = CFAbsoluteTimeGetCurrent();
for(i=0; i<count; i++){
    self.atomicFlag = 1;
}
timeCurrent = CFAbsoluteTimeGetCurrent();
printf("Atomic Set/Get used : %f\n", timeCurrent-timeBefore);

For atomic test case, set the same value to non copy property does not trigger any lock. It just simply return. So the lock performance for atomic is totally wrong. You should change the test code to this:

@property (atomic, assign) NSUInteger atomicFlag;

self.atomicFlag = count;

See objective-c runtime source code for property setter:
objc-accessor source code

下载下来文件是损坏的亲