[#83773] [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769 — usa@...
Issue #14108 has been updated by usa (Usaku NAKAMURA).
9 messages
2017/11/15
[#83774] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
usa@garbagecollect.jp wrote:
[#83775] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— "U.NAKAMURA" <usa@...>
2017/11/15
Hi, Eric
[#83779] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[#83781] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— "U.NAKAMURA" <usa@...>
2017/11/15
Hi, Eric,
[#83782] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[ruby-core:83922] [Ruby trunk Feature#4233][Closed] autoload Can't Require Gems
From:
mame@...
Date:
2017-11-28 14:36:43 UTC
List:
ruby-core #83922
Issue #4233 has been updated by mame (Yusuke Endoh).
Status changed from Assigned to Closed
Seems this issue was fixed. Closing.
----------------------------------------
Feature #4233: autoload Can't Require Gems
https://bugs.ruby-lang.org/issues/4233#change-67977
* Author: runpaint (Run Paint Run Run)
* Status: Closed
* Priority: Normal
* Assignee: nahi (Hiroshi Nakamura)
* Target version: next minor
----------------------------------------
=begin
Is it intentional that when used via `autoload`, `require` can't handle Gem names?
run@desktop:~/mir/ruby$ → ruby -e 'p require "nokogiri"'
true
run@desktop:~/mir/ruby$ → ruby -e 'autoload(:N, "nokogiri"); p N'
-e:1:in `<main>': cannot load such file -- nokogiri (LoadError)
=end
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>