Hi, I think there are very good reasons to make a class for it, some of them mentioned before: It allows you to: - debug values stored - add listeners for changes/updates - detect collisions - track where changes made are coming from, or at least when they happen - implement serialization/deserialization over a collection of these values - adheres to the idea of requesting rather than simply taking which is good practice in general
Greetz Hans -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Morten Barklund TBWA\Play Sent: Wednesday, February 01, 2006 9:43 AM To: Flashcoders mailing list Subject: Re: [Flashcoders] Tell me more about "_global" Steven Sacks wrote: > > Making a class for globals is lame. I don't get why people do stuff > like that. It's completely unnecessary. Here's how I make a > namespace for globals in one line. > > On frame one of the root timeline: > > _global.APP = {}; > > Wow. That was so hard. I can make the same, now it's just OOP: dynamic class APP {} Wow, that was easy - and without even mentioning _global. They do exactly the same; will you still recommend your version over mine? :) -- Morten Barklund - Information Architect - TBWA\Play Gothersgade 49, 4th floor - DK-1123 Copenhagen K, Denmark Phone: +45 7027 2227 - Fax: +45 3369 1174 _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
