Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Basically speaking, the rule simply doesn't work, or else it works by redefining what is meant by spiral (in which case, there's no point in it. Consider, for example: </p> <pre><code>int* a[10][15]; </code></pre> <p>The spiral rule would give a is an array[10] of pointer to array[15] of int, which is wrong. It the case you site, it doesn't work either; in fact, in the case of <code>signal</code>, it's not even clear where you should start the spiral.</p> <p>In general, it's easier to find examples of where the rule fails than examples where it works.</p> <p>I'm often tempted to say that parsing a C++ declaration is simple, but no body who has tried with complicated declarations would believe me. On the other hand, it's not as hard as it is sometimes made out to be. The secret is to think of the declaration exactly as you would an expression, but with a lot less operators, and a very simple precedence rule: all operators to the right have precedence over all operators to the left. In the absence of parentheses, this means process everything to the right first, then everything to the left, and process parentheses exactly as you would in any other expression. The actual difficulty is <em>not</em> the syntax per se, but that it results is some very complex and counterintuitive declarations, in particular where function return values and pointers to functions are involved: the first right, then left rule means that operators at a particular level are often widely separated, e.g.:</p> <pre><code>int (*f( /* lots of parameters */ ))[10]; </code></pre> <p>The final term in the expansion here is <code>int[10]</code>, but putting the <code>[10]</code> after the complete function specification is (at least to me) very unnatural, and I have to stop and work it out each time. (It's probably this tendency for logically adjacent parts to spread out that lead to the spiral rule. The problem is, of course, that in the absence of parentheses, they don't always spread out&mdash;anytime you see <code>[i][j]</code>, the rule is go right, then go right again, rather than spiral.)</p> <p>And since we're now thinking of declarations in terms of expressions: what do you do when an expression becomes too complicated to read? You introduce intermediate variables in order to make it easier to read. In the case of declarations, the "intermediate variables" are <code>typedef</code>. In particular, I would argue that any time part of the return type ends up after the function arguments (and a lot of other times as well), you should use a <code>typedef</code> to make the declaration simpler. (This is a "do as I say, not as I do" rule, however. I'm afraid that I'll occasionally use some very complex declarations.)</p>
    singulars
    1. This table or related slice is empty.
    1. POThe spiral rule about declarations — when is it in error?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJames Kanze
    1. USJames Kanze
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. This table or related slice is empty.
 

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