StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17935996
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-07-29T23:35:06.683
FavoriteCount
0
LastActivityDate
2013-07-29T23:35:06.683
LastEditDate
LastEditorUserId
0
OwnerUserId
699632
ParentId
17935617
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<a href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/statements.html#const" rel="nofollow"><code>const</code></a> A constant is constant. That means it does not change, because it is constant. The idea behind a constant is that you can be assured its value does not change during runtime. If you try to assign a new value to a constant, you will get an error like this: <blockquote> <code>1049: Illegal assignment to a variable specified as constant.</code> </blockquote> In your example, <code>RADIUS</code> is not re-calculated. In fact, that behaviour doesn't occur when you access any variable - unless you are accessing it via a getter that needs to calculate the result before returning it. An example of this might be a getter that returns the distance between two points. In your final example, you are assigning a <code>Point</code> to a constant. This behaves a little differently than you might expect. What you cannot do is go ahead and assign a new Point to the <code>MY_POINT</code>. What you can do however is modify the values of that Point. For example, you will be able to do this: <pre><code>MY_POINT.x = 10; </code></pre> Constants are best suited for storing primitive types (int, uint, Number, Boolean, String). In this case you would be better off creating separate constants to store the <code>x</code> and <code>y</code> of your Point, and omit creation of a Point: <pre><code>const POINT_X:int = 10; const POINT_Y:int = 15; </code></pre> <a href="http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/statements.html#static" rel="nofollow"><code>static</code></a> The <code>static</code> modifier is actually not related to constants, it is a separate keyword that adds the property or method being defined to the class definition rather than instances of that class. Because a constant is stateful and does not change, there is no reason to have a constant attached to every instance of a class. Constants are useful for adding readability and security when working with primitive data. Those constants can be stored as static members of a class acting as a collection of related constants, or a class that makes use of those constants as arguments of its methods. The <code>Event</code> class is a good example of this - it stores primitve data (strings) as static constants to represent the different event types, e.g. <code>Event.ACTIVATE</code>. When using methods that expect an event type, e.g. <code>addEventListener()</code>, we can refer to that constant rather than the primitive <code>"activate"</code>. This protects us against bugs, because the primitive allows spelling errors - if you make a typo accessing a constant, you will receive a compile-time error.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POStatic public constant ActionScript 3 good practices
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMarty
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.