The thought of changing multiple lines of code to go from static to non
would really suck; that drives the point home for me. Thanks for taking
the
time to explain it Spike!
That's that whole maintainability thing, which, in commercial software,
is usually just as or even more important than efficiency and optimization.
Incidentally, the way I handled that particular example was by making a
single dynamic class that can be instantiated as a particular locale, or can
change locales with a single method call, with a common set of functions and
loadable locale defenitions, which was instantiated in a singleton
"enviornment" class. That way, there is only ever one application
"enviornment", but potentially several different locales that can be used to
format dates and numbers through a common interface. It was way easier than
making 276 static classes for all the locales I had to support. ;-)
ryanm
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
