I've used namespaces like this in some of the libraries I've built before.
One of the best reasons for it is to clean up the API. If you're using FlashDevelop or another code
editor with code hints, you can see all of the available options as you type. If it belongs to
another namespace they won't show up, so it's perfect to keep the external stuff external, and the
internal stuff internal. Obviously you can use the "private" or "protected"
namespaces (because that's what they are) for this, but when a library gets complex you need to
access private values between classes.
Thus, namespace arcane. Make sense?
On Fri, 05 Feb 2010 10:14:57 -0800, Makc <[email protected]> wrote:
On Fri, Feb 5, 2010 at 7:27 PM, Howard Beware
<[email protected]> wrote:
I'm relatively new to AS3 and Away3D and I don't understand the use of
use namespace arcane;
What's the rationale behind this?
namespaced class members act like internal members but across the
packages. for example, QuadrantRiddleFilter class has access to
UV.weighted (when they are in different packages) because it uses
arcane namespace.
however, it seems the namespace is overused in away, e.g. some
variables in this namespace are not accessed from anywhere where using
namespace would make sense.
