cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   manucorporat
   Member

   ok, but between a ccArray and a CCArray?

   Posted 1 year ago #
2. 

   manucorporat
   Member

   Here is:
   http://github.com/manucorporat/cocos2d-iphone/commits/

   Posted 1 year ago #
3. 

   crmagicxxx
   Member

   I like this macro and started using it pretty much. Though I have one question...

   What you think about making CCARRAY_FOREACH iterating backwards? That way we can easily remove objects from array during iteration instead of making temporary mutable arrays or similar workarounds.

   Thanks

   Posted 1 year ago #
4. 

   riq
   Key Master

   @crmagicxxx: I think that it's possible to remove objects while iterating from a CCArray, or at least from the inner ccCArray.
   Also, I wouldn't modify the iteration direction since it might cause some bugs.

   regarding CCArray, this bug #901 is the one that is blocking v0.99.4-rc3 (last rc).

   But I can't fix it since I can't reproduce it on my machine :-( ... any volunteer ?

   Posted 1 year ago #
5. 

   Codemattic
   Moderator

   Maybe nodes could have a flag we could set that told cocos to remove it safely whenever cocos iterates through it next. So we wouldnt remove sprites directly, but just mark them for removal and cocos handles it sometime before the next tick.

   Posted 1 year ago #
6. 

   crmagicxxx
   Member

   It seems you can remove an object during the iteration, at least you'll not get a crash, but I think it's not done correctly. But I am not sure...

   Posted 1 year ago #
7. 

   Pearapps
   Member

   Has anyone done performance testing on the bug fixed "CCARRAY_FOREACH" - seems to be slower - any thoughts?

   Posted 1 year ago #
8. 

   Kronon
   Member

   http://www.learn-cocos2d.com/2010/09/array-performance-comparison-carray-ccarray-nsarray-nsmutablearray/

   Posted 8 months ago #
9. 

   ksjogo
   Member

   http://www.learn-cocos2d.com/2011/11/depth-ios-cocos2d-performance-analysis-test-project/
   Someone probably should look into insert.

   Posted 2 months ago #
10. 

    riq
    Key Master

    @jogo:
    https://github.com/cocos2d/cocos2d-iphone/blob/develop/CHANGELOG#L12

    Posted 2 months ago #
11. 

    cocojoe
    Member

    @jogo thanks for posting link, interesting read.

    Posted 2 months ago #
12. 

    cocos
    Member

    The problem with insert at index 0 is definitely real for CCArray.
    Do not worry if your array is small.

    // Test this loop for speed for the CCArray and NSMutableArray:
    

    for(i=0;i<testCount;i++)
    {
        [test insertObject:obj atIndex:0];
    }

    // Test results for iPod 1gen:
    

    testCount  = 100;
    Insert time is about 6 ms for both arrays (CCArray is slightly faster)
    
    testCount  = 200;
    Insert time is about 13 ms for both arrays (CCArray is slightly slower)
    
    If your array is big than rethink your algorithms. Penalty is huge:
    
    testCount  = 10000;
    NSMutableArray: insert time is about      85 ms
    CCArray:        insert time is about    3553 ms	<-- 3.5sec !!!! 3553/85 = 41.8

    Posted 2 months ago #
13. 

    cocos
    Member

    Inserting at 0 index:

    testCount  = 10000; // size of the array
    NSMutableArray: insert time at index 0 is about      85 ms
    CCArray:        insert time at index 0 is about    3553 ms	<-- 3.5sec !!!! 3553/85 = 41.8

    I hope it can be easily optimized - I did not look deeper into it yet.

    Posted 1 month ago #

RSS feed for this topic

Reply

You must log in to post.