[ruby-core:23718] Re: [Bug #1573] $0 behaves unexpectedly

Excerpts from Luiz Angelo Daros de Luca's message of Fri Jun 05 19:07:18 +0300 2009:
> Bug #1573: $0 behaves unexpectedly
> http://redmine.ruby-lang.org/issues/show/1573
> 
> Author: Morris Brodersen
> Status: Open, Priority: Normal
> Category: core
> ruby -v: ruby 1.9.1p0 (2009-01-30 revision 21907) [i386-mswin32]
> 
> consider two files, foo.rb and bar.rb, both simply contain: "p $0". i run "ruby
> -rbar.rb foo.rb".
> 
> using 1.8.6 and the same setup, the output is:
> 
> "foo.rb"
> "foo.rb"
> 
> using 1.9.1p0 the output is:
> 
> "ruby"
> "foo.rb"
> 
> as a developer, i would expect the old (1.8.6) behavior. i've had arguments
> that the new behavior is more "correct", as there is no actual script running
> when the requiring of bar.rb takes place. however, from this correctness, there
> arises no advantage whatsoever. i am strongly in favor of the old behavior.

I would argue that the 1.9 (and 1.8.7) version is a better
representation of the actual state of the program.

Further, though, I cannot see a valid use case where the
script being required with -r *should* know the name of
the assumed eventual script: to me, it implies a problem
with the design and/or the separation of responsibilities.

As always, there may be some use case I am missing?

The "$0 == __FILE__" trick obviously works the same in both
implementations.


Regards,
          Eero
--
Magic is insufficiently advanced technology.