Databases
StackOverflow2013
Postsdbo
POBest practices for runtime code generation in Ruby
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest practices for runtime code generation in Ruby
    primarykey
    data
    text
    <p>I recently started playing around with parsers and parser generators and their uses in DSL design. To get things started, and to kill two birds with one stone, I wrote a pure Ruby PEG parser DSL by stealing some ideas from peg.js. The difference is that peg.js will compile the grammar to JavaScript whereas my library uses the interpreter pattern combined with some syntax sugar that Ruby provides to do everything in pure Ruby. This adds some non-trivial overhead that I would like to avoid.</p> <p>To reduce some of the overhead I started thinking about compiling some of the parsing expressions that are generated into lower level representation. One idea I had was to use <code>eval</code> to evaluate the string representation of the code within the singleton class of some object. Here's some pseudo-code to demonstrate the process:</p> <pre><code># will be used to pass CompiledExpression instance to `eval` def get_binding(instance) instance.instance_eval { binding } end # an instance of this class will be used with `eval` # to define an `execute` method class CompiledExpression attr_reader :code_repr # need to instantiate with a string representation of # the code we are going to use to define the `execute` method def initialize(code) @code_repr = code end end # create the instance and define `execute` for that instance # by evaluating the code representation compiled_expr = CompiledExpression.new # first way eval "class &lt;&lt; self; def execute; " + "#{compiled_expr.code_repr}; end; end", get_binding(compiled_expr) # second way compiled_expr.instance_eval "class &lt;&lt; self; " + "def execute; #{compiled_expr.code_repr}: end; end" # third way compiled_expr.singleton_class.class_eval "def execute; " + "#{compiled_expr.code_repr}; end" # fourth way compiled_expr.instance_eval "def execute; " + "#{compiled_expr.code_repr}; end" </code></pre> <p>I want to know whether there are other/better approaches to accomplishing such code generation? I'm new to this stuff so I'm probably missing something obvious.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USchris
    1. USdavidk01
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest practices for runtime code generation in Ruby
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest practices for runtime code generation in Ruby
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBest practices for runtime code generation in Ruby
      1. USColin R
      1. VTFavorite
    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