[ruby-core:113975] [Ruby master Bug#19726] Script loadde twice when requiring self

Issue #19726 has been updated by Eregon (Benoit Daloze).


A similar case that I have found surprising is if e.g. I use a file for a quick test called like a stdlib, say `openssl.rb`, then `require 'openssl'` in that file would not require the stdlib but load the main script a second time, if `-I.` or so.
That's really unfortunate.

It seems pretty clear nobody wants to load the main script twice, so what's the compatibility issue with adding main script to $LOADED_FEATURES like other (require'd) files?

----------------------------------------
Bug #19726: Script loadde twice when requiring self
https://bugs.ruby-lang.org/issues/19726#change-103633

* Author: johannes (Johannes Krude)
* Status: Open
* Priority: Normal
* ruby -v:  ruby 3.3.0preview1 (2023-05-12 master a1b01e7701) [x86_64-linux]
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
The executed program is not added to `$LOADED_FEATURES` unexpectedly resulting in the program possibly being loaded twice:

a.rb:
```
#!/usr/bin/env ruby

require "./b"

C = 42

return unless __FILE__ == $0

puts C
```

b.rb:
```
require "./a"
```

This results in:
```
$ ./a.rb 
./a.rb:5: warning: already initialized constant C
/home/johannes/t/a.rb:5: warning: previous definition of C was here
42
```

Ruby version:
```
$ sudo docker run ruby:3.3.0-preview1 ruby --version
ruby 3.3.0preview1 (2023-05-12 master a1b01e7701) [x86_64-linux]
```

**This could be solved by always adding the executed program to `$LOADED_FEATURES`.**


As a workaround, executed programs can be prepended with:
```
require "pathname"
if __FILE__ == $0
	$LOADED_FEATURES << Pathname.new(__FILE__).expand_path.to_s
end
```



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/