> There must be equivalent Java functions somewhere (and ActionScript is > far more akin to Java than PHP or Ruby).
I think every and any are fine, to be honest. > But, as pointed out before, ActionScript is far more akin to Java, where > "equals" is something just about every single object has. Furthermore, > some Flash objects (e.g., Point), already use "equals". Finally, "eql" > looks a lot like "leq". What's leq? > "Deleting" means you are utterly destroying the object > --essentially forcing garbage collection. Ah, well this is where the point I made to Mike comes into play. I'm not destroying an element OF the Array, I'm deleting an element FROM the Array. Array.delete means delete an element of the Array because that's the scope of the delete method - it belongs to the Array and refers to the collection of objects, not the objects themselves. Permit me a Ted Stevens moment, if you will. An Array is a box that is self-aware of its contents and nothing else. If you remove an item from the box, from the Box's point of view, that item no longer exists - it's been deleted from the Box. Remove and delete are essentially synonymous. If I delete (or remove, as you say) an element from an Array, the Array takes up less memory, hence garbage collection is doing its job and I am utterly destroying the pointer's presence in the Array (not the pointer itself). I'm chocking this up to a fundamental difference of opinion about the theoretical (philosophical?) relationships of Objects in an OOP design pattern. Backspace and Delete, Enter and Return...which is right? :) _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com