Databases
StackOverflow2013
Postsdbo
PODRY way of re-raising same set of exceptions in multiple places
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODRY way of re-raising same set of exceptions in multiple places
    primarykey
    data
    text
    <p>short:</p> <p>Is there a way in Ruby to DRY-ify this:</p> <pre><code>def entry_point_one begin do_something rescue MySyntaxErrorOne, MySyntaxErrorTwo, MySyntaxErrorEtc =&gt; syn_err raise syn_err.exception(syn_err.message) end end def entry_point_two begin do_something_else rescue MySyntaxErrorOne, MySyntaxErrorTwo, MySyntaxErrorEtc =&gt; syn_err raise syn_err.exception(syn_err.message) end end </code></pre> <p>longer:</p> <p>I'm building an interpreter. This interpreter can be called using different entry points. If I feed this interpreter a 'dirty' string, I expect it to raise an error. However, it would be nice if I don't get spammed by the by the entire back trace of every method called directly or indirectly by do_something, especially since the interpreter makes use of recursion.</p> <p>As you can see in the above snippet, I already know a way to re raise an error and thereby removing the back trace. What I would like do is remove the duplication in the above example. The closest I have come thus far is this:</p> <pre><code>def entry_point_one re_raise_known_exceptions {do_something} end def entry_point_two re_raise_known_exceptions {do_something_else} end def re_raise_known_exceptions yield rescue MySyntaxErrorOne, MySyntaxErrorTwo, MySyntaxErrorEtc =&gt; syn_err raise syn_err.exception(syn_err.message) end </code></pre> <p>But that makes the method re-raise-known-exceptions show up in the back trace.</p> <p>edit: I guess what I want would be something like a C pre-processing macro</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USxian
    1. USPatrick Huizinga
    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
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODRY way of re-raising same set of exceptions in multiple places
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODRY way of re-raising same set of exceptions in multiple places
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODRY way of re-raising same set of exceptions in multiple places
      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