# Binding#eval \_\_LINE\_\_ and \_\_FILE\_\_ in Ruby 1.9.1

**URL:** <https://www.ruby-forum.com/t/binding-eval-line-and-file-in-ruby-1-9-1/178450>\
**Category:** Ruby\
**Created:** [November 4, 2009, 9:39pm UTC](https://www.ruby-forum.com/t/binding-eval-line-and-file-in-ruby-1-9-1/178450 "2009-11-04T21:39:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tcsnide](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/eb8c5e/32.png) [@tcsnide](https://www.ruby-forum.com/u/tcsnide)\
**Post date:** [November 4, 2009, 9:39pm UTC](https://www.ruby-forum.com/t/binding-eval-line-and-file-in-ruby-1-9-1/178450/1 "2009-11-04T21:39:31Z")

</div>

Ok. One last question in today’s debugging for 1.9 session.

Using Bindging#eval, **LINE** and **FILE** always appear the same:

binding.eval(‘ **FILE** ’) #=\> “(eval)”  
binding.eval(‘ **LINE** ’) #=\> 1

Do we not want the **LINE** and **FILE** of the binding call in the  
binding’s context? That is what 1.8.7 does.

So, is it a bug? Or has this been changed for some reason?