debug utility macro rp() (rp_m()) and bp() are introduced.
* rp(obj) shows obj information w/o any side-effect to STDERR.
* rp_m(m, obj) is similar to rp(obj), but show m before.
* bp() is alias of ruby_debug_breakpoint(), which is registered
as a breakpoint in run.gdb (used by `make gdb` or make gdb-ruby`).
As `make test-tool` does not use gems, and no Rubygems stuffs is
needed, so moved such things to test/runner.rb. Also no longer
nees `--test-target-dir` option.
And `make test-tool` includes `make test-testframework`.
This change may be arguable because I'm unsure who is an intended user
of `make check`: a normal user, or Ruby-core developer. Normal users
don't have to run `make test-tool` for testing their installation, but
Ruby committers should run it before they commit anything.
In this case, I'd be conservative; `make check` includes `test-tool`.
If normal users often report a failure of `make test-tool`, then we can
consider to split `make check` for two sets of target users.
tool/test/runner.rb had been copied from test/runner.rb.
test/runner.rb was for `make test-all`, and tool/test/runner.rb was for
`make test-testframework` and `make test-tool`.
But I want to avoid the code clones.
This change makes tool/test/runner.rb support --test-target-dir option
which allows tool/test/runner.rb to run `make test-all`.
Now we can remove test/runner.rb.
because v0.14.18 was actually not working with `make run`.
In `make run`, `Gem` is defined but `Gem::Version` isn't.
v0.14.19 checks `defined?(Gem::Version)` instead of `defined?(Gem)`.
This reverts commit 4c0e21add7
because we're not using /bin/bash.
See 11d3986d65 and
1b2b0e1f24 to know its context.
In short, 4c0e21add7 does not work on
Ubuntu.
Since 72ad092960, we cannot run full `make benchmark`
because default BENCH_RUBY is miniruby and it fails to require 'time'.
Using miniruby for benchmark by default seems reasonable for some cases,
but now it's just bothering for people running full `make benchmark`.
This reverts commit 05bc14d81a.
We have decided that the cost of reintroducing support for 1.8
BASERUBY outweighs the benefit. If you are still using 1.8 and want
to build master/trunk, build and install the latest release, and use
that as BASERUBY.
is yes.
We ignored the failure status of file2lastrev.rb on 73da429c36, but it
was for an environment without BASERUBY. I think we should skip running
file2lastrev.rb on HAVE_BASERUBY=no, and run it and check the status on
HAVE_BASERUBY=yes.
Otherwise we may have an ignored arbitrary error of file2lastrev.rb on
HAVE_BASERUBY=yes environment.
Unicode version 12.1.0 was officially released on May 7th, 2019.
There were no changes at all from the "real" beta
published shortly after the new era name "Reiwa" was announced.
So we can switch UNICODE_BETA back to NO.
common.mk: switch UNICODE_BETA back to NO
tool/downloader.rb: add additional conditions to avoid an error
when moving from beta to final
Koichi Sasada
Takashi Kokubun
Nobuyoshi Nakada
Yusuke Endoh
Hiroshi SHIBATA
Samuel Williams
Jeremy Evans
Martin Dürst