Use more memory efficient method of storing numbers

[KorvinSzanto]

SplObjectStorage is better suited for what we're trying to do in NumberCollection.

[mikeytag]

Agreed. Anything that smells of proceduralness should be removed immediately. I'm looking at you arrays.

[ultimape]

Why don't we store the values within a Java Bean. Then we can persist them to a database and get all sorts of delicious metrics.

Also, is this threadsafe?

[an-empty-string]

Why not just use a hashing algorithm to store the numbers in a map, keyed by string index?

[gquemener]

I would recommend a hash key generator then

[KorvinSzanto]

Its becoming clear that we need to rearchitect the way we handle number collections. On May 20, 2014 8:49 AM, "Gildas Quéméner" [email protected] wrote:

I would recommend a hash key generator then

— Reply to this email directly or view it on GitHubhttps://github.com/Herzult/SimplePHPEasyPlus/pull/6#issuecomment-43644265 .

[an-empty-string]

I'm thinking, that instead of a hash generator, perhaps we should architect our own NumberLinkedListNode class, and then use a doubly-linked circular linked list. This maximizes the efficiency of number operations while allowing us to effectively use the object-oriented paradigm. Thoughts?