[#104169] [Ruby master Feature#17938] Keyword alternative for boolean positional arguments — matheusrichardt@...

Issue #17938 has been reported by matheusrich (Matheus Richard).

12 messages 2021/06/04

[#104213] [Ruby master Feature#17942] Add a `initialize(public @a, private @b)` shortcut syntax for defining public/private accessors for instance vars — tyler@...

Issue #17942 has been reported by TylerRick (Tyler Rick).

6 messages 2021/06/09

[#104288] [Ruby master Bug#17992] Upstreaming the htmlentities gem into CGI#.(un)escape_html — alexandermomchilov@...

Issue #17992 has been reported by AMomchilov (Alexander Momchilov).

9 messages 2021/06/15

[#104338] [Ruby master Misc#17997] DevelopersMeeting20210715Japan — mame@...

Issue #17997 has been reported by mame (Yusuke Endoh).

10 messages 2021/06/17

[#104361] [Ruby master Bug#18000] have_library doesn't work when ruby is compiled with --disable-shared --disable-install-static-library — jean.boussier@...

Issue #18000 has been reported by byroot (Jean Boussier).

9 messages 2021/06/18

[#104401] [Ruby master Feature#18007] Help developers of C extensions meet requirements in "doc/extension.rdoc" — mike.dalessio@...

Issue #18007 has been reported by mdalessio (Mike Dalessio).

16 messages 2021/06/25

[#104430] [Ruby master Bug#18011] `Method#parameters` is incorrect for forwarded arguments — josh.cheek@...

Issue #18011 has been reported by josh.cheek (Josh Cheek).

12 messages 2021/06/29

[ruby-core:104363] [Ruby master Feature#14378] Increase Fixnum range on Windows from 31 bits to 63 bits

From: merch-redmine@...
Date: 2021-06-18 19:31:26 UTC
List: ruby-core #104363
Issue #14378 has been updated by jeremyevans0 (Jeremy Evans).

Backport deleted (2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN)
ruby -v deleted (2.5.0)
Subject changed from On windows, RUBY_FIXNUM_MAX of 64 bits ruby  is 32 bits to Increase Fixnum range on Windows from 31 bits to 63 bits
Tracker changed from Bug to Feature

This issue is still present in the master branch.  However, the range of T_FIXNUM is an implementation detail, especially since  Integer unification in Ruby 2.4, so I do not think this is a bug.  I think we wouldn't be opposed to increasing the range of Fixnum on 64-bit Windows, but I consider that a feature request.

----------------------------------------
Feature #14378: Increase Fixnum range on Windows from 31 bits to 63 bits
https://bugs.ruby-lang.org/issues/14378#change-92592

* Author: HfCloud (Xiangyu Shi)
* Status: Open
* Priority: Normal
----------------------------------------
On windows, start an IRB of a 64-bits ruby, enter these code:

~~~ruby
(1<<29).equal?(1<<29) 
#=>true

(1<<30).equal?(1<<30)
#=>false
~~~

So, it is that FIXNUM of the 64-bits ruby is a 32-bits data?
But my friend try these code on linux platform and all got true(it means FIXNUM is 64bits) 
Then I opened ruby/ruby.h and found this:

~~~ ruby
#define RUBY_FIXNUM_MAX (LONG_MAX>>1)
~~~

The LONG_MAX of my compiler(msvc140, vs2017) is 2147483647, and the ruby which is installed by ruby-installer also have the same problem.





-- 
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>

In This Thread

Prev Next