Ruby Issue Tracking System

01/15/2023

11:00 PM Ruby Revision 4617b40f (git): fix typo in comments / autodoc

replace _socktype_ with _type_ in the comments RickHull (Rick Hull)

12/04/2017

04:09 AM Ruby Bug #14148: Longstanding behavior regarding correspondence of toplevel with Object is surprising

Hi @mame,
I agree that the change from warning to NameError is intended, and this behavior change is not the concern:
> I don't think is a problem for 2.5. The overall behavior seems consistent with 2.4, if surprising. My surprise ... RickHull (Rick Hull)

12/02/2017

06:18 PM Ruby Bug #14148: Longstanding behavior regarding correspondence of toplevel with Object is surprising

I edited the title of this issue. I reported this initially as 2.5.0 issue, as I discovered it while playing around with the 2.5.0 changes regarding toplevel constant lookup. Now, this ticket is more about surprising behavior in genera... RickHull (Rick Hull)

08:07 AM Ruby Bug #14148: Longstanding behavior regarding correspondence of toplevel with Object is surprising

After some clarifying discussions with @matthewd, I don't think is a problem for 2.5. The overall behavior seems consistent with 2.4, if surprising. My surprise mostly revolves around the strange correspondence of toplevel with Object.... RickHull (Rick Hull)

01:36 AM Ruby Bug #14148: Longstanding behavior regarding correspondence of toplevel with Object is surprising

Further down the rabbit hole, ruby 2.4.0p0:
~~~ ruby
class BasicObject
X = 1
end
String::X #=> 1
class Object
X = 2
end
String::X #=> 2
# warning: toplevel constant X referenced by String::X
~~~
On ruby 2.5.0-... RickHull (Rick Hull)

12:36 AM Ruby Bug #14148: Longstanding behavior regarding correspondence of toplevel with Object is surprising

Behavior on 2.4.0p0:
~~~ ruby
module Kernel
X = 1
end
String::X #=> 1
X = 2
String::X #=> 2
# warning: toplevel constant X referenced by String::X
~~~
~~~ ruby
class Object
X = 1
end
String.superclass #=> Ob... RickHull (Rick Hull)

12:28 AM Ruby Bug #14148: Longstanding behavior regarding correspondence of toplevel with Object is surprising

Expected behavior: `String::X` should continue to evaluate to `1` after `X = 2` at the toplevel
Actual behavior: `String::X` results in NameError after `X = 2` at the toplevel
more strangeness:
~~~ ruby
class Object
X = 1
e... RickHull (Rick Hull)

12:14 AM Ruby Bug #14148 (Closed): Longstanding behavior regarding correspondence of toplevel with Object is surprising

~~~ ruby
module Kernel
X = 1
end
puts String::X
X = 2
puts String::X
~~~
~~~
$ ruby test.rb
1
Traceback (most recent call last):
test.rb:9:in `<main>': uninitialized constant String::X (NameError)
Did you mean? X
... RickHull (Rick Hull)

12/01/2017

11:47 PM Ruby Feature #11547: remove top-level constant lookup

Hm, this is surprising:
~~~ ruby
module Kernel
X = 1
end
puts String::X
X = 2
puts String::X
~~~
~~~
$ ruby test.rb
1
Traceback (most recent call last):
test.rb:9:in `<main>': uninitialized constant String::X (Na... RickHull (Rick Hull)

01/24/2017

11:33 AM Ruby Feature #13153 (Open): Inconsistent sprintf formatting for 0 value

```ruby
0.upto(5).map { |i| "%#0.2x" % i }
# expect: ["0x00", "0x01", "0x02", "0x03", "0x04", "0x05"]
# actual: ["00", "0x01", "0x02", "0x03", "0x04", "0x05"]
```
Notice that the 0x is omitted when i == 0. The 0x prefix is sp... RickHull (Rick Hull)