Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A short introduction:</p> <p>You don't need the Mod-instance, if you define @@foo outside <code>initialize</code>.</p> <p>You don't need the Mod class to get the problem:</p> <pre><code>class Foo def yielder p 2 yield "hello" end end foo = Foo.new foo.yielder do |hello| puts hello end foo.class.send(:define_method,:yielder) do p 1 yield "new hello" end foo.yielder do |hello| puts hello end </code></pre> <p>You may shorten your example again:</p> <pre><code>class Foo end foo = Foo.new foo.class.send(:define_method,:yielder) do yield "new hello" end foo.yielder do |hello| puts hello end </code></pre> <p>This is the same as:</p> <pre><code>class Foo define_method(:yielder) do yield "new hello" end end foo = Foo.new foo.yielder do |hello| puts hello end </code></pre> <p>End of Introduction.</p> <p>And now, I'm not sure if I understood correct what you want (and if I understand ruby correct ;) ) <code>define_method</code> accepts a block and use it as method body. If the new method should receive a block on its own, you must define it in the interface of the definition and call it:</p> <pre><code>class Foo define_method(:yielder) do | &amp;prc | prc.call("new hello") end end foo = Foo.new foo.yielder do |hello| puts hello end </code></pre> <p>Or the same logic in your example:</p> <pre><code>class Foo def yielder yield "hello" end end class Mod def initialize @@foo = Foo.new end def self.foo @@foo end end worker = Mod.new Mod.foo.yielder do |hello| puts hello end Mod.foo.class.send(:define_method,:yielder) do | &amp;prc | prc.call "new hello" end Mod.foo.yielder do |hello| puts hello end </code></pre> <p>To make the code more robust, I would recommend some checks with <code>block_given?</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. PORe-defined method with a yield throws no block given
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USknut
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORe-defined method with a yield throws no block given
      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. VTAcceptedByOriginator
    1. COIt boils down to that sending `define_method` doesn't allow the same implicit block method signature.
      singulars
      1. PO
      1. USDave Newton
    2. COReal world use requires the way it fails some times. Hence this question, but thank you very much for a well elaborated answer.
      singulars
      1. PO
      1. USpatrick
    3. COOh, and it also mess up for rspec this one, I bet this case is interesting for the rspec maintainser, I will file this as a issue there with your fine example. I have also filed a issue on ruby itself with a link here.
      singulars
      1. PO
      1. USpatrick
 

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