StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10997835
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-12T13:35:00.353
FavoriteCount
0
LastActivityDate
2012-06-13T07:04:21.360
LastEditDate
2012-06-13T07:04:21.360
LastEditorUserId
493928
OwnerUserId
192444
ParentId
10996669
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
Before I answer your question I want to address <blockquote> BTW, that code terminates without volatile on JRE7 </blockquote> This can change if you were to deploy the same application with different runtime arguments. Hoisting isn't necessarily a default implementation for JVMs so it can work in one and not in another. To answer your question there is nothing preventing the Java compiler from executing your latter example like so <pre><code>@Override public void run() { if(b.getField()){ while(true) { System.err.println("Waiting..."); try { Thread.sleep(1000); } catch(InterruptedException ie) { return; } } } } </code></pre> It is still sequentially consistent and thus maintains Java's guarantees - you can read specifically <a href="http://docs.oracle.com/javase/specs/jls/se7/html/jls-17.html" rel="nofollow">17.4.3</a>: <blockquote> Among all the inter-thread actions performed by each thread t, the program order of t is a total order that reflects the order in which these actions would be performed according to the intra-thread semantics of t. A set of actions is sequentially consistent if all actions occur in a total order (the execution order) that is consistent with program order, and furthermore, each read r of a variable v sees the value written by the write w to v such that: </blockquote> In other words - So long as a thread will see the read and write of a field in the same order regardless of the compiler/memory re ordering it is considered sequentially consistent.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POjava: `volatile` private fields with getters and setters
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USkhachik
UserOwnerUserId
1. USJohn Vint
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POjava: `volatile` private fields with getters and setters
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.