Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POC++0x lambdas coding style
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRichard Corden
    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. VTDownMod
    1. COAlthough what you say is true, you could make exactly the same mistake if you wrote a for loop, and did int xl = *iterator; sum += x1;. Nobody's demanding explicit capture in that situation. In cases where the lifetime of the lambda is confined to the local scope, I think that implicit capture is no more (nor less) dangerous than the fact that simple braces inherit the surrounding automatic scope. It's when the lambda is going to live on that I think you want to be explicit what's captured (and deduce that what is not captured can safely die at end of lexical scope).
      singulars
      1. PO
      1. USSteve Jessop
    2. COIt is not important that the error can exist in other constructs. This is an additional advantage of lambda's, in that you can reduce the visibility of names more than is possible for a "for loop". There are many ways that name hiding/visibility can result in subtle errors. One goal of a coding standard is to reduce the cases that can cause a problem and you'll find several rules regarding name hiding and reduction of name visibility in standards such as JSF++, MISRA C/C++. I can see this being another.
      singulars
      1. PO
      1. USRichard Corden
    3. COBut it doesn't actually reduce the visibility compared with the equivalent functor, it just prevents it being extended. That's not an advantage, it's mitigation. So on this point I think lambdas are (very slightly) worse than functors, in that if you think default capture is bad, you now have to ban it and police the ban. But yes, perhaps better than structured programming.
      singulars
      1. PO
      1. USSteve Jessop
 

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