StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6732876
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-07-18T12:30:40.503
FavoriteCount
0
LastActivityDate
2014-05-18T13:14:28.380
LastEditDate
2014-05-18T13:14:28.380
LastEditorUserId
385378
OwnerUserId
385378
ParentId
6726589
PostTypeId
2
Score
32
ViewCount
0
LastEditorDisplayName
text
Body
This behavior could be classified as bug, so you should definitely not rely on it. The (simplified) conditions for the message not to be thrown on a function call are as follows (see the <a href="http://lxr.php.net/search?q=ZEND_SEND_VAR_NO_REF&project=PHP_5_3" rel="nofollow">definition of the opcode <code>ZEND_SEND_VAR_NO_REF</code></a>): <ul> <li>the argument is not a function call (or if it is, it returns by reference), and</li> <li>the argument is either a reference or it has reference count 1 (if it has reference count 1, it's turned into a reference).</li> </ul> Let's analyze these in more detail. <h3>First point is true (not a function call)</h3> Due to the additional parentheses, PHP no longer detects that the argument is a function call. When parsing a <a href="http://lxr.php.net/xref/PHP_5_3/Zend/zend_language_parser.y#non_empty_function_call_parameter_list" rel="nofollow">non empty function argument list</a> there are three possibilities for PHP: <ul> <li>An <code>expr_without_variable</code></li> <li>A <code>variable</code></li> <li>(A <code>&</code> followed by a <code>variable</code>, for the removed call-time pass by reference feature)</li> </ul> When writing just <code>get_array()</code> PHP sees this as a <code>variable</code>. <code>(get_array())</code> on the other hand does not qualify as a <code>variable</code>. It is an <code>expr_without_variable</code>. This ultimately affects the way the code compiles, namely the extended value of the opcode <code>SEND_VAR_NO_REF</code> will no longer include the flag <code>ZEND_ARG_SEND_FUNCTION</code>, which is the way the function call is detected in the opcode implementation. <h3>Second point is true (the reference count is 1)</h3> At several points, the Zend Engine allows non-references with reference count 1 where references are expected. These details should not be exposed to the user, but unfortunately they are here. In your example you're returning an array that's not referenced from anywhere else. If it were, you would still get the message, i.e. this second point would not be true. So the following very similar example does not work: <pre><code><?php $a = array(); function get_array() { return $GLOBALS['a']; } return reset((get_array())); </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POParentheses altering semantics of function call result
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNikiC
UserOwnerUserId
1. USNikiC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POParentheses altering semantics of function call result
 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
 VTUpMod
CommentsPostId
1. COFantastic. And I realise now that the AST isn't particularly irrelevant. Thank you :)
 singulars
 PostPostId
 PO
 UserUserId
 USLightness Races in Orbit
2. COThe bug-report is: https://bugs.php.net/bug.php?id=55222
 singulars
 PostPostId
 PO
 UserUserId
 UShakre

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.