StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5720490
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-04-19T17:49:41.390
FavoriteCount
0
LastActivityDate
2011-04-19T17:56:57.390
LastEditDate
2011-04-19T17:56:57.390
LastEditorUserId
713425
OwnerUserId
713425
ParentId
5720030
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
If you try running the code below and look at the backtrace output you will see that PHP converts instanceFunc() to a static method when called in a static context. However, in an instance context it will treat it as a instance call. If you introduce instance variables in to the mix (remove commented out lines) then a fatal error is encountered when called instanceFunc() from a static call. This implies that PHP allows all methods that are static in nature (no instance variables are worked with) to be called from a static context, as soon as this contract is broken however an error will be produced. Therefore the use of static functions seems to be only good practice in keeping with other Object Orientated languages. With regards to staticFunc() both calls show that PHP interprets these as static calls, which is to be expected. <pre><code>class A { private $x = 5; private $y = 6; private $z; public function instanceFunc() { //$this->z = $this->y * $this->x; //echo $this->z; var_dump(reset(debug_backtrace())); } public static function staticFunc() { var_dump(reset(debug_backtrace())); } } $a = new A(); A::instanceFunc(); // static call of intended instance method $a->instanceFunc(); // instance call of instance method A::staticFunc(); $a->staticFunc(); </code></pre> Example output (code running with comments): <pre><code>array(6) { ["file"]=> string(59) "test.php" ["line"]=> int(19) ["function"]=> string(12) "instanceFunc" ["class"]=> string(1) "A" ["type"]=> string(2) "::" ["args"]=> array(0) { } } array(7) { ["file"]=> string(59) "test.php" ["line"]=> int(22) ["function"]=> string(12) "instanceFunc" ["class"]=> string(1) "A" ["object"]=> object(A)#8 (3) { ["x:private"]=> int(5) ["y:private"]=> int(6) ["z:private"]=> NULL } ["type"]=> string(2) "->" ["args"]=> array(0) { } } array(6) { ["file"]=> string(59) "test.php" ["line"]=> int(24) ["function"]=> string(10) "staticFunc" ["class"]=> string(1) "A" ["type"]=> string(2) "::" ["args"]=> array(0) { } } array(6) { ["file"]=> string(59) "test.php" ["line"]=> int(26) ["function"]=> string(10) "staticFunc" ["class"]=> string(1) "A" ["type"]=> string(2) "::" ["args"]=> array(0) { } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPHP's static member and instance member seems no different. Why PHP does so(Without warning)?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGordyD
UserOwnerUserId
1. USGordyD
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. 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
CommentsPostId
1. COInteresting stuff on the backtrace, +1. In light of the fact the doing this will throw an E_STRICT error only, I am assuming this is maintained for some legacy/backwards compatibility reasons - with an intent to eventually eliminate it. Otherwise, the "convert this method to static" behavior is nonsense - you're totally correct about it, but it is nonsense all the same!
 singulars
 PostPostId
 PO
 UserUserId
 USChris Baker
2. COI agree, it is nonsensical, but PHP was not born an OO language and so I imagine your suspicions of this 'bug' existing for legacy reasons is correct.
 singulars
 PostPostId
 PO
 UserUserId
 USGordyD

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.