motion-yapper 0.0.3 → 0.1.0

data/vendor/Pods/BuildHeaders/CocoaLumberjack/DDAbstractDatabaseLogger.h

@@ -1,102 +0,0 @@
-#import <Foundation/Foundation.h>
-
-#import "DDLog.h"
-
-/**
- * Welcome to Cocoa Lumberjack!
- * 
- * The project page has a wealth of documentation if you have any questions.
- * https://github.com/CocoaLumberjack/CocoaLumberjack
- * 
- * If you're new to the project you may wish to read the "Getting Started" wiki.
- * https://github.com/CocoaLumberjack/CocoaLumberjack/wiki/GettingStarted
- * 
- * 
- * This class provides an abstract implementation of a database logger.
- * 
- * That is, it provides the base implementation for a database logger to build atop of.
- * All that is needed for a concrete database logger is to extend this class
- * and override the methods in the implementation file that are prefixed with "db_".
-**/
-
-@interface DDAbstractDatabaseLogger : DDAbstractLogger {
-@protected
-    NSUInteger saveThreshold;
-    NSTimeInterval saveInterval;
-    NSTimeInterval maxAge;
-    NSTimeInterval deleteInterval;
-    BOOL deleteOnEverySave;
-    
-    BOOL saveTimerSuspended;
-    NSUInteger unsavedCount;
-    dispatch_time_t unsavedTime;
-    dispatch_source_t saveTimer;
-    dispatch_time_t lastDeleteTime;
-    dispatch_source_t deleteTimer;
-}
-
-/**
- * Specifies how often to save the data to disk.
- * Since saving is an expensive operation (disk io) it is not done after every log statement.
- * These properties allow you to configure how/when the logger saves to disk.
- * 
- * A save is done when either (whichever happens first):
- * 
- * - The number of unsaved log entries reaches saveThreshold
- * - The amount of time since the oldest unsaved log entry was created reaches saveInterval
- * 
- * You can optionally disable the saveThreshold by setting it to zero.
- * If you disable the saveThreshold you are entirely dependent on the saveInterval.
- * 
- * You can optionally disable the saveInterval by setting it to zero (or a negative value).
- * If you disable the saveInterval you are entirely dependent on the saveThreshold.
- * 
- * It's not wise to disable both saveThreshold and saveInterval.
- * 
- * The default saveThreshold is 500.
- * The default saveInterval is 60 seconds.
-**/
-@property (assign, readwrite) NSUInteger saveThreshold;
-@property (assign, readwrite) NSTimeInterval saveInterval;
-
-/**
- * It is likely you don't want the log entries to persist forever.
- * Doing so would allow the database to grow infinitely large over time.
- * 
- * The maxAge property provides a way to specify how old a log statement can get
- * before it should get deleted from the database.
- * 
- * The deleteInterval specifies how often to sweep for old log entries.
- * Since deleting is an expensive operation (disk io) is is done on a fixed interval.
- * 
- * An alternative to the deleteInterval is the deleteOnEverySave option.
- * This specifies that old log entries should be deleted during every save operation.
- * 
- * You can optionally disable the maxAge by setting it to zero (or a negative value).
- * If you disable the maxAge then old log statements are not deleted.
- * 
- * You can optionally disable the deleteInterval by setting it to zero (or a negative value).
- * 
- * If you disable both deleteInterval and deleteOnEverySave then old log statements are not deleted.
- * 
- * It's not wise to enable both deleteInterval and deleteOnEverySave.
- * 
- * The default maxAge is 7 days.
- * The default deleteInterval is 5 minutes.
- * The default deleteOnEverySave is NO.
-**/
-@property (assign, readwrite) NSTimeInterval maxAge;
-@property (assign, readwrite) NSTimeInterval deleteInterval;
-@property (assign, readwrite) BOOL deleteOnEverySave;
-
-/**
- * Forces a save of any pending log entries (flushes log entries to disk).
-**/
-- (void)savePendingLogEntries;
-
-/**
- * Removes any log entries that are older than maxAge.
-**/
-- (void)deleteOldLogEntries;
-
-@end

data/vendor/Pods/BuildHeaders/CocoaLumberjack/DDContextFilterLogFormatter.h

@@ -1,63 +0,0 @@
-#import <Foundation/Foundation.h>
-#import "DDLog.h"
-
-/**
- * Welcome to Cocoa Lumberjack!
- * 
- * The project page has a wealth of documentation if you have any questions.
- * https://github.com/CocoaLumberjack/CocoaLumberjack
- * 
- * If you're new to the project you may wish to read the "Getting Started" page.
- * https://github.com/CocoaLumberjack/CocoaLumberjack/wiki/GettingStarted
- * 
- * 
- * This class provides a log formatter that filters log statements from a logging context not on the whitelist.
- * 
- * A log formatter can be added to any logger to format and/or filter its output.
- * You can learn more about log formatters here:
- * https://github.com/CocoaLumberjack/CocoaLumberjack/wiki/CustomFormatters
- * 
- * You can learn more about logging context's here:
- * https://github.com/CocoaLumberjack/CocoaLumberjack/wiki/CustomContext
- *
- * But here's a quick overview / refresher:
- * 
- * Every log statement has a logging context.
- * These come from the underlying logging macros defined in DDLog.h.
- * The default logging context is zero.
- * You can define multiple logging context's for use in your application.
- * For example, logically separate parts of your app each have a different logging context.
- * Also 3rd party frameworks that make use of Lumberjack generally use their own dedicated logging context.
-**/
-@interface DDContextWhitelistFilterLogFormatter : NSObject <DDLogFormatter>
-
-- (id)init;
-
-- (void)addToWhitelist:(int)loggingContext;
-- (void)removeFromWhitelist:(int)loggingContext;
-
-- (NSArray *)whitelist;
-
-- (BOOL)isOnWhitelist:(int)loggingContext;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-/**
- * This class provides a log formatter that filters log statements from a logging context on the blacklist.
-**/
-@interface DDContextBlacklistFilterLogFormatter : NSObject <DDLogFormatter>
-
-- (id)init;
-
-- (void)addToBlacklist:(int)loggingContext;
-- (void)removeFromBlacklist:(int)loggingContext;
-
-- (NSArray *)blacklist;
-
-- (BOOL)isOnBlacklist:(int)loggingContext;
-
-@end

data/vendor/Pods/BuildHeaders/CocoaLumberjack/DDDispatchQueueLogFormatter.h

@@ -1,128 +0,0 @@
-#import <Foundation/Foundation.h>
-#import <libkern/OSAtomic.h>
-#import "DDLog.h"
-
-
-/**
- * Welcome to Cocoa Lumberjack!
- * 
- * The project page has a wealth of documentation if you have any questions.
- * https://github.com/CocoaLumberjack/CocoaLumberjack
- * 
- * If you're new to the project you may wish to read the "Getting Started" page.
- * https://github.com/CocoaLumberjack/CocoaLumberjack/wiki/GettingStarted
- * 
- * 
- * This class provides a log formatter that prints the dispatch_queue label instead of the mach_thread_id.
- * 
- * A log formatter can be added to any logger to format and/or filter its output.
- * You can learn more about log formatters here:
- * https://github.com/CocoaLumberjack/CocoaLumberjack/wiki/CustomFormatters
- * 
- * A typical NSLog (or DDTTYLogger) prints detailed info as [<process_id>:<thread_id>].
- * For example:
- * 
- * 2011-10-17 20:21:45.435 AppName[19928:5207] Your log message here
- * 
- * Where:
- * - 19928 = process id
- * -  5207 = thread id (mach_thread_id printed in hex)
- * 
- * When using grand central dispatch (GCD), this information is less useful.
- * This is because a single serial dispatch queue may be run on any thread from an internally managed thread pool.
- * For example:
- * 
- * 2011-10-17 20:32:31.111 AppName[19954:4d07] Message from my_serial_dispatch_queue
- * 2011-10-17 20:32:31.112 AppName[19954:5207] Message from my_serial_dispatch_queue
- * 2011-10-17 20:32:31.113 AppName[19954:2c55] Message from my_serial_dispatch_queue
- * 
- * This formatter allows you to replace the standard [box:info] with the dispatch_queue name.
- * For example:
- * 
- * 2011-10-17 20:32:31.111 AppName[img-scaling] Message from my_serial_dispatch_queue
- * 2011-10-17 20:32:31.112 AppName[img-scaling] Message from my_serial_dispatch_queue
- * 2011-10-17 20:32:31.113 AppName[img-scaling] Message from my_serial_dispatch_queue
- * 
- * If the dispatch_queue doesn't have a set name, then it falls back to the thread name.
- * If the current thread doesn't have a set name, then it falls back to the mach_thread_id in hex (like normal).
- * 
- * Note: If manually creating your own background threads (via NSThread/alloc/init or NSThread/detachNeThread),
- * you can use [[NSThread currentThread] setName:(NSString *)].
-**/
-@interface DDDispatchQueueLogFormatter : NSObject <DDLogFormatter> {
-@protected
-    
-    NSString *dateFormatString;
-}
-
-/**
- * Standard init method.
- * Configure using properties as desired.
-**/
-- (id)init;
-
-/**
- * The minQueueLength restricts the minimum size of the [detail box].
- * If the minQueueLength is set to 0, there is no restriction.
- * 
- * For example, say a dispatch_queue has a label of "diskIO":
- * 
- * If the minQueueLength is 0: [diskIO]
- * If the minQueueLength is 4: [diskIO]
- * If the minQueueLength is 5: [diskIO]
- * If the minQueueLength is 6: [diskIO]
- * If the minQueueLength is 7: [diskIO ]
- * If the minQueueLength is 8: [diskIO  ]
- * 
- * The default minQueueLength is 0 (no minimum, so [detail box] won't be padded).
- * 
- * If you want every [detail box] to have the exact same width,
- * set both minQueueLength and maxQueueLength to the same value.
-**/
-@property (assign) NSUInteger minQueueLength;
-
-/**
- * The maxQueueLength restricts the number of characters that will be inside the [detail box].
- * If the maxQueueLength is 0, there is no restriction.
- * 
- * For example, say a dispatch_queue has a label of "diskIO":
- *
- * If the maxQueueLength is 0: [diskIO]
- * If the maxQueueLength is 4: [disk]
- * If the maxQueueLength is 5: [diskI]
- * If the maxQueueLength is 6: [diskIO]
- * If the maxQueueLength is 7: [diskIO]
- * If the maxQueueLength is 8: [diskIO]
- * 
- * The default maxQueueLength is 0 (no maximum, so [detail box] won't be truncated).
- * 
- * If you want every [detail box] to have the exact same width,
- * set both minQueueLength and maxQueueLength to the same value.
-**/
-@property (assign) NSUInteger maxQueueLength;
-
-/**
- * Sometimes queue labels have long names like "com.apple.main-queue",
- * but you'd prefer something shorter like simply "main".
- * 
- * This method allows you to set such preferred replacements.
- * The above example is set by default.
- * 
- * To remove/undo a previous replacement, invoke this method with nil for the 'shortLabel' parameter.
-**/
-- (NSString *)replacementStringForQueueLabel:(NSString *)longLabel;
-- (void)setReplacementString:(NSString *)shortLabel forQueueLabel:(NSString *)longLabel;
-
-@end
-
-/**
- * Method declarations that make it easier to extend/modify DDDispatchQueueLogFormatter
-**/
-@interface DDDispatchQueueLogFormatter (OverridableMethods)
-
-- (NSString *)stringFromDate:(NSDate *)date;
-- (NSString *)queueThreadLabelForLogMessage:(DDLogMessage *)logMessage;
-- (NSString *)formatLogMessage:(DDLogMessage *)logMessage;
-
-@end
-

data/vendor/Pods/BuildHeaders/CocoaLumberjack/DDFileLogger.h

@@ -1,369 +0,0 @@
-#import <Foundation/Foundation.h>
-#import "DDLog.h"
-
-@class DDLogFileInfo;
-
-/**
- * Welcome to Cocoa Lumberjack!
- * 
- * The project page has a wealth of documentation if you have any questions.
- * https://github.com/CocoaLumberjack/CocoaLumberjack
- * 
- * If you're new to the project you may wish to read the "Getting Started" wiki.
- * https://github.com/CocoaLumberjack/CocoaLumberjack/wiki/GettingStarted
- * 
- * 
- * This class provides a logger to write log statements to a file.
-**/
-
-
-// Default configuration and safety/sanity values.
-// 
-// maximumFileSize         -> DEFAULT_LOG_MAX_FILE_SIZE
-// rollingFrequency        -> DEFAULT_LOG_ROLLING_FREQUENCY
-// maximumNumberOfLogFiles -> DEFAULT_LOG_MAX_NUM_LOG_FILES
-// 
-// You should carefully consider the proper configuration values for your application.
-
-#define DEFAULT_LOG_MAX_FILE_SIZE     (1024 * 1024)   //  1 MB
-#define DEFAULT_LOG_ROLLING_FREQUENCY (60 * 60 * 24)  // 24 Hours
-#define DEFAULT_LOG_MAX_NUM_LOG_FILES (5)             //  5 Files
-
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-// The LogFileManager protocol is designed to allow you to control all aspects of your log files.
-// 
-// The primary purpose of this is to allow you to do something with the log files after they have been rolled.
-// Perhaps you want to compress them to save disk space.
-// Perhaps you want to upload them to an FTP server.
-// Perhaps you want to run some analytics on the file.
-// 
-// A default LogFileManager is, of course, provided.
-// The default LogFileManager simply deletes old log files according to the maximumNumberOfLogFiles property.
-// 
-// This protocol provides various methods to fetch the list of log files.
-// 
-// There are two variants: sorted and unsorted.
-// If sorting is not necessary, the unsorted variant is obviously faster.
-// The sorted variant will return an array sorted by when the log files were created,
-// with the most recently created log file at index 0, and the oldest log file at the end of the array.
-// 
-// You can fetch only the log file paths (full path including name), log file names (name only),
-// or an array of DDLogFileInfo objects.
-// The DDLogFileInfo class is documented below, and provides a handy wrapper that
-// gives you easy access to various file attributes such as the creation date or the file size.
-
-@protocol DDLogFileManager <NSObject>
-@required
-
-// Public properties
-
-/**
- * The maximum number of archived log files to keep on disk.
- * For example, if this property is set to 3,
- * then the LogFileManager will only keep 3 archived log files (plus the current active log file) on disk.
- * Once the active log file is rolled/archived, then the oldest of the existing 3 rolled/archived log files is deleted.
- * 
- * You may optionally disable deleting old/rolled/archived log files by setting this property to zero.
-**/
-@property (readwrite, assign) NSUInteger maximumNumberOfLogFiles;
-
-// Public methods
-
-- (NSString *)logsDirectory;
-
-- (NSArray *)unsortedLogFilePaths;
-- (NSArray *)unsortedLogFileNames;
-- (NSArray *)unsortedLogFileInfos;
-
-- (NSArray *)sortedLogFilePaths;
-- (NSArray *)sortedLogFileNames;
-- (NSArray *)sortedLogFileInfos;
-
-// Private methods (only to be used by DDFileLogger)
-
-- (NSString *)createNewLogFile;
-
-@optional
-
-// Notifications from DDFileLogger
-
-- (void)didArchiveLogFile:(NSString *)logFilePath;
-- (void)didRollAndArchiveLogFile:(NSString *)logFilePath;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-/**
- * Default log file manager.
- * 
- * All log files are placed inside the logsDirectory.
- * If a specific logsDirectory isn't specified, the default directory is used.
- * On Mac, this is in ~/Library/Logs/<Application Name>.
- * On iPhone, this is in ~/Library/Caches/Logs.
- * 
- * Log files are named "<bundle identifier> <date> <time>.log"
- * Example: com.organization.myapp 2013-12-03 17-14.log
- * 
- * Archived log files are automatically deleted according to the maximumNumberOfLogFiles property.
-**/
-@interface DDLogFileManagerDefault : NSObject <DDLogFileManager>
-{
-    NSUInteger maximumNumberOfLogFiles;
-    NSString *_logsDirectory;
-}
-
-- (id)init;
-- (instancetype)initWithLogsDirectory:(NSString *)logsDirectory;
-
-/*
- * Methods to override.
- *
- * Log files are named "<bundle identifier> <date> <time>.log"
- * Example: com.organization.myapp 2013-12-03 17-14.log
- *
- * If you wish to change default filename, you can override following two methods.
- * - newLogFileName method would be called on new logfile creation.
- * - isLogFile: method would be called to filter logfiles from all other files in logsDirectory.
- *   You have to parse given filename and return YES if it is logFile.
- *
- * **NOTE**
- * newLogFileName returns filename. If appropriate file already exists, number would be added
- * to filename before extension. You have to handle this case in isLogFile: method.
- *
- * Example:
- * - newLogFileName returns "com.organization.myapp 2013-12-03.log",
- *   file "com.organization.myapp 2013-12-03.log" would be created.
- * - after some time "com.organization.myapp 2013-12-03.log" is archived
- * - newLogFileName again returns "com.organization.myapp 2013-12-03.log",
- *   file "com.organization.myapp 2013-12-03 2.log" would be created.
- * - after some time "com.organization.myapp 2013-12-03 1.log" is archived
- * - newLogFileName again returns "com.organization.myapp 2013-12-03.log",
- *   file "com.organization.myapp 2013-12-03 3.log" would be created.
-**/
-- (NSString *)newLogFileName;
-- (BOOL)isLogFile:(NSString *)fileName;
-
-/* Inherited from DDLogFileManager protocol:
-
-@property (readwrite, assign) NSUInteger maximumNumberOfLogFiles;
-
-- (NSString *)logsDirectory;
-
-- (NSArray *)unsortedLogFilePaths;
-- (NSArray *)unsortedLogFileNames;
-- (NSArray *)unsortedLogFileInfos;
-
-- (NSArray *)sortedLogFilePaths;
-- (NSArray *)sortedLogFileNames;
-- (NSArray *)sortedLogFileInfos;
-
-*/
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-/**
- * Most users will want file log messages to be prepended with the date and time.
- * Rather than forcing the majority of users to write their own formatter,
- * we will supply a logical default formatter.
- * Users can easily replace this formatter with their own by invoking the setLogFormatter method.
- * It can also be removed by calling setLogFormatter, and passing a nil parameter.
- * 
- * In addition to the convenience of having a logical default formatter,
- * it will also provide a template that makes it easy for developers to copy and change.
-**/
-@interface DDLogFileFormatterDefault : NSObject <DDLogFormatter>
-{
-    NSDateFormatter *dateFormatter;
-}
-
-- (id)init;
-- (instancetype)initWithDateFormatter:(NSDateFormatter *)dateFormatter;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-@interface DDFileLogger : DDAbstractLogger <DDLogger>
-{
-    __strong id <DDLogFileManager> logFileManager;
-    
-    DDLogFileInfo *currentLogFileInfo;
-    NSFileHandle *currentLogFileHandle;
-    
-    dispatch_source_t currentLogFileVnode;
-    dispatch_source_t rollingTimer;
-    
-    unsigned long long maximumFileSize;
-    NSTimeInterval rollingFrequency;
-}
-
-- (id)init;
-- (instancetype)initWithLogFileManager:(id <DDLogFileManager>)logFileManager;
-
-/**
- * Log File Rolling:
- * 
- * maximumFileSize:
- *   The approximate maximum size to allow log files to grow.
- *   If a log file is larger than this value after a log statement is appended,
- *   then the log file is rolled.
- * 
- * rollingFrequency
- *   How often to roll the log file.
- *   The frequency is given as an NSTimeInterval, which is a double that specifies the interval in seconds.
- *   Once the log file gets to be this old, it is rolled.
- * 
- * Both the maximumFileSize and the rollingFrequency are used to manage rolling.
- * Whichever occurs first will cause the log file to be rolled.
- * 
- * For example:
- * The rollingFrequency is 24 hours,
- * but the log file surpasses the maximumFileSize after only 20 hours.
- * The log file will be rolled at that 20 hour mark.
- * A new log file will be created, and the 24 hour timer will be restarted.
- * 
- * You may optionally disable rolling due to filesize by setting maximumFileSize to zero.
- * If you do so, rolling is based solely on rollingFrequency.
- * 
- * You may optionally disable rolling due to time by setting rollingFrequency to zero (or any non-positive number).
- * If you do so, rolling is based solely on maximumFileSize.
- * 
- * If you disable both maximumFileSize and rollingFrequency, then the log file won't ever be rolled.
- * This is strongly discouraged.
-**/
-@property (readwrite, assign) unsigned long long maximumFileSize;
-@property (readwrite, assign) NSTimeInterval rollingFrequency;
-
-/**
- * The DDLogFileManager instance can be used to retrieve the list of log files,
- * and configure the maximum number of archived log files to keep.
- * 
- * @see DDLogFileManager.maximumNumberOfLogFiles
-**/
-@property (strong, nonatomic, readonly) id <DDLogFileManager> logFileManager;
-
-
-// You can optionally force the current log file to be rolled with this method.
-// CompletionBlock will be called on main queue.
-
-- (void)rollLogFileWithCompletionBlock:(void (^)())completionBlock;
-
-// Method is deprecated. Use rollLogFileWithCompletionBlock: method instead.
-
-- (void)rollLogFile __attribute((deprecated));
-
-// Inherited from DDAbstractLogger
-
-// - (id <DDLogFormatter>)logFormatter;
-// - (void)setLogFormatter:(id <DDLogFormatter>)formatter;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-/**
- * DDLogFileInfo is a simple class that provides access to various file attributes.
- * It provides good performance as it only fetches the information if requested,
- * and it caches the information to prevent duplicate fetches.
- * 
- * It was designed to provide quick snapshots of the current state of log files,
- * and to help sort log files in an array.
- * 
- * This class does not monitor the files, or update it's cached attribute values if the file changes on disk.
- * This is not what the class was designed for.
- * 
- * If you absolutely must get updated values,
- * you can invoke the reset method which will clear the cache.
-**/
-@interface DDLogFileInfo : NSObject
-{
-    __strong NSString *filePath;
-    __strong NSString *fileName;
-    
-    __strong NSDictionary *fileAttributes;
-    
-    __strong NSDate *creationDate;
-    __strong NSDate *modificationDate;
-    
-    unsigned long long fileSize;
-}
-
-@property (strong, nonatomic, readonly) NSString *filePath;
-@property (strong, nonatomic, readonly) NSString *fileName;
-
-@property (strong, nonatomic, readonly) NSDictionary *fileAttributes;
-
-@property (strong, nonatomic, readonly) NSDate *creationDate;
-@property (strong, nonatomic, readonly) NSDate *modificationDate;
-
-@property (nonatomic, readonly) unsigned long long fileSize;
-
-@property (nonatomic, readonly) NSTimeInterval age;
-
-@property (nonatomic, readwrite) BOOL isArchived;
-
-+ (instancetype)logFileWithPath:(NSString *)filePath;
-
-- (instancetype)initWithFilePath:(NSString *)filePath;
-
-- (void)reset;
-- (void)renameFile:(NSString *)newFileName;
-
-#if TARGET_IPHONE_SIMULATOR
-
-// So here's the situation.
-// Extended attributes are perfect for what we're trying to do here (marking files as archived).
-// This is exactly what extended attributes were designed for.
-// 
-// But Apple screws us over on the simulator.
-// Everytime you build-and-go, they copy the application into a new folder on the hard drive,
-// and as part of the process they strip extended attributes from our log files.
-// Normally, a copy of a file preserves extended attributes.
-// So obviously Apple has gone to great lengths to piss us off.
-// 
-// Thus we use a slightly different tactic for marking log files as archived in the simulator.
-// That way it "just works" and there's no confusion when testing.
-// 
-// The difference in method names is indicative of the difference in functionality.
-// On the simulator we add an attribute by appending a filename extension.
-// 
-// For example:
-// "mylog.txt" -> "mylog.archived.txt"
-// "mylog"     -> "mylog.archived"
-
-- (BOOL)hasExtensionAttributeWithName:(NSString *)attrName;
-
-- (void)addExtensionAttributeWithName:(NSString *)attrName;
-- (void)removeExtensionAttributeWithName:(NSString *)attrName;
-
-#else
-
-// Normal use of extended attributes used everywhere else,
-// such as on Macs and on iPhone devices.
-
-- (BOOL)hasExtendedAttributeWithName:(NSString *)attrName;
-
-- (void)addExtendedAttributeWithName:(NSString *)attrName;
-- (void)removeExtendedAttributeWithName:(NSString *)attrName;
-
-#endif
-
-- (NSComparisonResult)reverseCompareByCreationDate:(DDLogFileInfo *)another;
-- (NSComparisonResult)reverseCompareByModificationDate:(DDLogFileInfo *)another;
-
-@end