[Detrius]

I'm just wondering if this is bad programming style... I have an object that is generally going to be used in a multithreaded environment. I want this object to be lockable. I'm thinking of just subclassing NSLock instead of instantiating an NSLock inside of it and passing the lock requests to that. Am I just crazy here? For some reason, I'm just looking at this idea and thinking it's a silly thing to do. Any opinions?

Note: this will be a single object referenced by multiple threads.

[leperkuhn]

Originally posted by Detrius:
I'm just wondering if this is bad programming style... I have an object that is generally going to be used in a multithreaded environment. I want this object to be lockable. I'm thinking of just subclassing NSLock instead of instantiating an NSLock inside of it and passing the lock requests to that. Am I just crazy here? For some reason, I'm just looking at this idea and thinking it's a silly thing to do. Any opinions?

Note: this will be a single object referenced by multiple threads.

you would only want to subclass NSLock if you want to inherit it's functions, ie: if you are changing the way it performs a lock...