| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
If `build` directory exists, `rake build` is `Rake::FileTask`.
So skip if exists.
|
|
|
|
| |
Float should not be compared by identity.
|
|
|
|
|
| |
A path starts with '/' is not an absolute path on Windows, because
of drive letter or UNC.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Because `.ext/common` is not relative from top source directory.
Fix failures with out-of-place build directory.
|
|
|
|
| |
because some features are already loaded.
|
| |
|
| |
|
|
|
|
| |
Co-Authored-By: Matt Valentine-House <31869+eightbitraptor@users.noreply.github.com>
|
| |
|
|
|
|
| |
https://github.com/ruby/irb/commit/502c590925
|
|
|
|
|
|
|
|
| |
* using the appropriciate exception instead of `break` so that the session
can be continue after the `irb_source` and `irb_load` commands
* suppress extra new line due to one more `#prompt` call
https://github.com/ruby/irb/commit/bdefaa7cfd
|
|
|
|
|
|
|
| |
* tweak some methods not to raise exception after `#close`
* use it in `IRB::IrbLoader#{source_file,load_file}
https://github.com/ruby/irb/commit/ec2947acbd
|
| |
|
|
|
|
|
| |
As `RUBY_TRY_CFLAGS` restores `CFLAGS`, appending to the variable
in its block has no effect.
|
| |
|
|
|
|
|
| |
https://github.com/ruby/ruby/pull/4100#pullrequestreview-576059827
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
|
|
| |
cf: https://github.com/ruby/ruby/pull/4100#pullrequestreview-575952836
|
|
|
|
|
|
|
|
| |
They are no longer how Object#clone/Object#dup are defined. In fact
DUPSETUP is not used from anywhere. CLONESETUP has only one usage.
Let's not expose them to extension libraries.
cf https://github.com/ruby/ruby/pull/4100#discussion_r563481718
|
|
|
|
| |
Makes no sense any longer.
|
|
|
|
| |
Makes no sense any longer.
|
|
|
|
|
|
|
|
|
| |
See also https://gcc.gnu.org/gcc-6/changes.html
Clang has this feature when __has_extension(enumerator_attributes) is
set.
MSVC has #pragma deprecated instead.
|
|
|
|
|
|
|
|
| |
matz said in [ruby-core:94979]:
> 3.0:
> * taint/trust/untaint/untrust non-verbose warning when called
This is it, for C extensions.
|
|
|
|
|
|
|
|
|
| |
Now that RUBY_FL_TAINT is recycled to become new RUBY_FL_SHAREABLE.
Setting/clearing this flag from extension libraries break Ractor.
Especially problematic one is OBJ_INFECT, which would make non-shareable
objects travel across Ractor boundaries.
Such operations should just be prohibited.
|
|
|
|
|
| |
It seems I broke them in commit 9e6e39c3512f7a962c44dc3729c98a0f8be90341
Sorry!
|
| |
|
|
|
|
|
|
| |
Just like rb_define_class_id_under(). Also makes
rb_define_module_under() consistent with rb_define_class_under() in the
same regard.
|
|
|
| |
Link was correct; its target was incorrect; now fixed.
|
|
|
|
|
|
|
|
| |
after this commit turned it off globally.
888cf28a7e3a07fc0a41688777a40910654005ad
Co-authored-by: peterzhu2118 <peter@peterzhu.ca>
|
| |
|
|
|
|
|
|
|
|
| |
[A previous commit](b59077eecf912a16efefc0256f6e94a000ce3888) removes some macro definitions that are used when RGENGC_CHECK_MODE >=4 because they were using data stored against objspace, which is not ractor safe
This commit reinstates those macro definitions, using the current ractor
Co-authored-by: peterzhu2118 <peter@peterzhu.ca>
|
| |
|
|
|
|
|
|
|
| |
Although it was used just to suppress an "unsed argument" warning
in the same manner as other bison-provided functions, it has been
dropped since Bision 3.7.5. And we always suppress that
warnings.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/2a6c22da63
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/ad8cf37d72
|
| |
|
| |
|
|
|
|
|
| |
This reverts commit 80bad36989bbc4ad6167fe9670327f95b78089ce,
because a few CI machines fail continuously.
|
|
|
|
|
|
|
|
|
| |
For each `make check`, rubygems test makes "tmp" directory and
some "gem_generate_index..." directories remain there.
* Do not create a (fixed name) directory in the current working
directory
* Should remove its own temporary directory
|
|
|
|
|
|
|
|
|
|
| |
`RDoc::Parser::ChangeLog` mis-parses ChangeLog generated by
git-log, because of too heuristic `Time.parse`.
For instance, "commit 8187228de0142d3ac7950b7d977c2849e934c637"
results in "8187-08-16", that is, day 228 in the year 8187.
https://github.com/ruby/rdoc/commit/9711e6f6d9
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/455715e930
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/1821628076
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/5d3e153963
|
|
|
|
|
|
|
| |
* add 3 levels to headings
* prefix commit log to labels to make unique IDs
https://github.com/ruby/rdoc/commit/5074c13209
|