Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Prototypes aren't bad if used correctly. The difficulty is that Perl's prototypes don't work the way people often expect them to. People with a background in other programming languages tend to expect prototypes to provide a mechanism for checking that function calls are correct: that is, that they have the right number and type of arguments. Perl's prototypes are not well-suited for this task. It's the <em>misuse</em> that's bad. Perl's prototypes have a singular and very different purpose:</p> <p><strong>Prototypes allow you to define functions that behave like built-in functions.</strong></p> <ul> <li>Parentheses are optional.</li> <li>Context is imposed on the arguments.</li> </ul> <p>For example, you could define a function like this:</p> <pre><code>sub mypush(\@@) { ... } </code></pre> <p>and call it as</p> <pre><code>mypush @array, 1, 2, 3; </code></pre> <p>without needing to write the <code>\</code> to take a reference to the array.</p> <p>In a nutshell, prototypes let you create your own syntactic sugar. For example the Moose framework uses them to emulate a more typical OO syntax.</p> <p>This is very useful but prototypes are very limited:</p> <ul> <li>They have to be visible at compile-time.</li> <li>They can be bypassed.</li> <li>Propagating context to arguments can cause unexpected behavior.</li> <li>They can make it difficult to call functions using anything other than the strictly prescribed form.</li> </ul> <p>See <a href="http://perldoc.perl.org/perlsub.html#Prototypes" rel="noreferrer">Prototypes</a> in perlsub for all the gory details.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy are Perl 5's function prototypes bad?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USikegami
    1. USMichael Carman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy are Perl 5's function prototypes bad?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI've accepted this answer because I feel it best answers the question - prototypes aren't intrinsically bad, it's just how you use them.
      singulars
      1. PO
      1. USAlnitak
    2. COMoose prototypes on the otherhand, are /awesome/ http://p3rl.org/MooseX::Declare http://p3rl.org/MooseX::Method::Signatures
      singulars
      1. PO
      1. USKent Fredric
    3. CO[Far More Than Everything You Ever Wanted to Know about Perl Prototypes](http://www.perlmonks.org/?node_id=861966).
      singulars
      1. PO
      1. UStchrist
 

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