Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Actually I think the following version is even more commonly seen:</p> <pre><code>def each @items.each { |i| yield i } end </code></pre> <p>This is equivalent to your first code sample. There is however a subtle difference between this and your second version:</p> <pre><code>class Test def initialize(items) @items = items end def each1 @items.each { |i| yield i } end def each2(&amp;block) @items.each(&amp;block) end end </code></pre> <p>Observe:</p> <pre><code>irb(main):053:0&gt; Test.new([1,2,3]).each2 =&gt; #&lt;Enumerator: [1, 2, 3]:each&gt; irb(main):054:0&gt; Test.new([1,2,3]).each1 LocalJumpError: no block given (yield) from (irb):43:in `block in each1' from (irb):43:in `each' from (irb):43:in `each1' from (irb):54 from /usr/bin/irb:12:in `&lt;main&gt;' </code></pre> <p>The version that delegates the block to the underlying iterable actually returns an enumerator if no block is given, which is very nice. It allows us to write stuff like this:</p> <pre><code>irb(main):055:0&gt; Test.new([1,2,3]).each2.map { |x| x + 1 } =&gt; [2, 3, 4] </code></pre> <p>To achieve the same with our explicit version, we'd have to adapt it like this:</p> <pre><code>def each1 return enum_for(:each1) unless block_given? @items.each { |i| yield i } end </code></pre> <p>Which is even more verbose. Bottomline: Delegate the block to an underlying enumerable whenever possible, to save yourself from code duplication and from subtle gotchas like these.</p> <p>By the way, now that you realize the two-folded nature of your <code>each</code> method, it would make sense to name it differently. For example, you could follow the example of methods like <code>String#chars</code> or <code>IO#lines</code> and call your method <code>items</code>:</p> <pre><code>def items(&amp;block) @items.each(&amp;block) end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POBlock linking in Enumerable's each, allowed?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNiklas B.
    1. USNiklas B.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBlock linking in Enumerable's each, allowed?
      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. COThank you, your 3rd code example showed differences to me :) Looks like, i was right :)
      singulars
      1. PO
      1. USBubonic Pestilence
 

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