On 12/30/05, Nathan Derksen <[EMAIL PROTECTED]> wrote: > Yah, that's why it is so much cleaner just to have an associative > array as a private property within your class, and create addItem(), > getItem(), and removeItem() methods to manage that associative array. > That way you also don't have to worry about the names of added > properties possibly colliding with existing property/method names > within the class.
most definitely - and is the way i'm working it. just sucks that i can't catch a mistake that _might_ be made because of the associative array call. g. -- weblog: broadcast.artificialcolors.com blazePDF: www.blazepdf.com band: www.cutratebox.com _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
