Why does this rescue syntax work?

Question

Ok so I have this method of an application I am working with and it works in production. My question why does this work? Is this new Ruby syntax?

def edit
  load_elements(current_user) unless current_user.role?(:admin)

  respond_to do |format|
    format.json { render :json => @user }   
    format.xml  { render :xml => @user }
    format.html
  end

rescue ActiveRecord::RecordNotFound
  respond_to_not_found(:json, :xml, :html)
end

Nyasaland

See also #1543172 – Vinaya

Answer 1

rescues do not need to be tied to an explicit begin when they're in a method, that's just the way the syntax is defined. For examples, see #19 here and this SO question, as well as the dupe above.

Demirep

Answer 2

rescue can work alone . no need of begin and end always .

You can use rescue in its single line form to return a value when other things on the line go awry:

h = { :age => 10 }
h[:name].downcase                         # ERROR
h[:name].downcase rescue "No name"  

Eyler

This uses it as a statement modifier, though, which isn't the OP's question. You're correct, of course, but it doesn't directly answer the question. – Demirep

Answer 3

rescue word is part of method definition

But in controllers better to rescue errors with rescue_from

Vomit

Answer 4

try this

def edit
  begin
    load_elements(current_user) unless current_user.role?(:admin)

    respond_to do |format|
      format.json { render :json => @user }   
      format.xml  { render :xml => @user }
      format.html
    end

  rescue ActiveRecord::RecordNotFound
    respond_to_not_found(:json, :xml, :html)
  end
end

Ringo

It's perfectly legal to use a rescue inside a method definition (and implicit begin) without an explicit begin. – Demirep