Databases
StackOverflow2013
Postsdbo
POOnly variables can be passed by reference
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOnly variables can be passed by reference
    primarykey
    data
    text
    <p>I had the bright idea of using a custom error handler which led me down a rabbit hole.</p> <p>Following code gives (with and without custom error handler): <strong>Fatal error: Only variables can be passed by reference</strong></p> <pre><code>function foo(){ $b=array_pop(array("a","b","c")); return $b; } print_r(foo()); </code></pre> <p>Following code gives (<strong>only with a custom error handler</strong>): <strong>(2048) Only variables should be passed by reference</strong></p> <pre><code>function foo(){ $a=explode( '/' , 'a/b/c'); $c=array_pop(array_slice($a,-2,1)); return $c; } print_r(foo()); </code></pre> <p>The second one worries me since I have a lot of 'compact' code. So, I either ditch the bright idea of using a custom error handler (to improve my logging module) or expand all my code.</p> <p>Anyone with better ideas? Also, WTF?</p> <p><strong>UPDATE</strong>:</p> <p>Thanks to the answers I've learnt something about how php does error handling. The confusion of E_ALL not including E_STRICT (php 5) is not cool.</p> <p>On top of all this, creating your own custom error handler enables E_STRICT by default and thats where problems start.</p> <p>The moral of the story is to use your own error handler to catch them ALL and use the error constants (E_STRICT, E_USER_WARNING, E_USER_ERROR, etc.) to do your filtering.</p> <p>As for the 'memory corruption issue' with variable references and certain functions, what can I say? Doubly uncool. I'll (which doesn't mean you should) ignore E_STRICT in my error handler and life goes on.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USzaf
    1. USzaf
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOnly variables can be passed by reference
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POOnly variables can be passed by reference
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POOnly variables can be passed by reference
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO$b=current(array_reverse(array("a","b","c"))); // yes, it's silly, but it works :)
      singulars
      1. POOnly variables can be passed by reference
      1. USMSpreij
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload