Bernie wrote: Not sure how (or if it’s worth trying) to get around that in NSLog.incl.

Haven't tried here but since Steve's demo is all Objective-C, the NSLog.incl could be omitted and the NSLog() function would revert to the standard and print to the OS Console log. Maybe not convenient but it's an option. 

On a side note, I notice Xcode’s console is limited to around 32K of data for each NSLog call. So,in Steve’s demo, doing a NSLog(@"%@",mymutarr); before the array is emptied, truncates the data in Xcode console.

Xcode has more debug options, so NSLog limitations aren't a big concern. For example, the debug pane allows selection of a specific array index( or dictionary key/value pair ) which can then be printed( via contextual menu - see screen print )

However, my test results using Steve's code ( moved to Xcode 7 under OS X 10.11.6 ) exhibit an additional anomaly.

My applicationDidFinishLaunching with the following code:

-(void)applicationDidFinishLaunching:(NSNotification*)notification {
    @autoreleasepool {
        mymutarr = [[NSMutableArray alloc]initWithCapacity:0];
        NSDictionary *itemDict = @{@"key1": @"value1", @"key2": @"value2", @"key3": @"value3", @"key4": @"value4", @"key5": @"value5"};
        for(int i=0; i<150000; i++) {
            [mymutarr addObject:itemDict];
        [mymutarr release];
doesn't display mymutarr in the debug pane ( notice the screen print above 'itemDict' shows ). Since my playing has been superficial, it's likely I've overlooked something. I'd look deeper but have more pressing items right now. Let me know where I was stupid.


To unsubscribe, send ANY message to: futurebasic-unsubscribe@... To access the list archives, go to: