In short, the question is how important is it for me to call FSEventStreamStop (and similar followups) if it's just a cleanup thing as the app is quitting?
the long explanation:
I'm working on an app where a class of objects are correlated to a set of files in the filesystem; basically, for each file that's present in a particular location, I create one instance of the class. What I'd like to set up is so that I can do somethings like
[myclass instanceNamed:aname];
The thought was that the easiest way to do this would be to have the class (not one of its instances) maintain a list of the possible objects that can be returned, along with using fsevents to keep that list up to date. Starting fsevents can then easily be done either in +initialize, or the first time that +instanceNamed: is invoked. But there isn't a deallocation equivalent of +initialize as far as I know, so I can't think how I'd run cleanup code that's associated with the class rather than with one of its instances. Thus the question, does it matter if I cleanup the FSEventsStream before the app quits? (alternatively, if someone knows how to write cleanup code for the class...).
Top
