Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>As xil3 wrote, most people do look at a reference (that's what they're for) when they code. I personally have the php.net search tool installed on Firefox. I also have a search keyword set up for it. So I can just type <code>php array</code> or <code>php array_slice</code> into the address bar and it will take me to the <a href="http://us3.php.net/manual/en/language.types.array.php" rel="nofollow noreferrer">Arrays page</a> and <a href="http://us2.php.net/array_splice" rel="nofollow noreferrer">the documentation for <code>array_slice()</code></a> automatically. Aptana also gives you tooltips about each function, but they're fairly brief, out of necessity.</p> <p>Generally, the functions you use regularly you will remember how to use. The ones you don't or haven't used in a while you'll just have to look up. However, as a general rule, most of the array functions that are for modifying arrays are usually passed by ref, e.g.:</p> <pre><code>array_pop() array_push() array_shift() array_unshift() array_walk() asort() array_multisort() </code></pre> <p>Whereas the ones that make computations using multiple arrays or are extracting something from the array generally are passed by value, e.g.:</p> <pre><code>// multiple array inputs array_diff() array_merge() array_combine() // extraction array_values() array_keys() array_unique() array_sum() </code></pre> <p>Of course, there are some that break the rules or have ambiguous names, like <code>array_reverse()</code>, and I often still get <code>array_map()</code> and <code>array_walk()</code> confused (the latter is by ref), but for the most part it becomes intuitive after a while.</p> <p><strong>Edit:</strong> The PHP.net search tool can be <a href="http://mycroft.mozdev.org/search-engines.html?name=php.net" rel="nofollow noreferrer">found on MyCroft</a>. I use the one labeled "PHP Function List - en" by Lucas.</p>
 

Querying!

 
Guidance

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