Age | Commit message (Collapse) | Author |
|
Use of TOKEN_PASTE was a bad idea at the first place. Just use ##
everywhere. Nobody practically lacks token pasting.
Notes:
Merged: https://github.com/ruby/ruby/pull/4371
|
|
|
|
|
|
|
|
|
|
On 32-bit Android:
* `st_dev`/`st_rdev` are not `dev_t`
* `st_mode` is not `mode_t`
|
|
|
|
Update the start entry skipping all already deleted entries.
Fixes performance issue of `Hash#first` in a certain case.
|
|
|
|
|
|
|
|
This reverts commit bd7430c7aacd135419609eec72e3889cd00a6f73.
No rakelib in ruby itself.
|
|
https://github.com/ruby/optparse/commit/cccb28e0de
|
|
https://github.com/ruby/optparse/commit/8be031b539
|
|
https://github.com/ruby/optparse/commit/4ff48f24c9
|
|
- Added example in "Argument Converters"; it doesn't seem right for a tutorial to have no example in one of its topics (and instead just linking elsewhere).
- Added section "Command-Line Abbreviations."
- Added section "Keyword Argument into," showing how to:
- Collect options.
- Check for missing options.
- Provide option defaults.
https://github.com/ruby/optparse/commit/39d39676c4
|
|
* Resolve shared mixed_names.rb
* Add long option with negation
* Show --help for all examples
* Table of contents for tutorial
* Move argument converters to separate rdoc
* Add references to argument_converters.rdoc
* Tune up argument converters
* Change explicit links to auto-links
https://github.com/ruby/optparse/commit/c91ed8d33d
|
|
https://github.com/ruby/optparse/commit/9a2352c1c9
|
|
|
|
This step confused me when trying to compile Ruby after 5 years, so it
should be avoided unless you need static linking.
|
|
Non-gcc compilers tend to have this intrinsic these days, e.g. xlc
has `__sync` builtins.
Notes:
Merged: https://github.com/ruby/ruby/pull/4372
|
|
A workaround for `-f` option of AIX xlc compiler which works only
on linking.
Notes:
Merged: https://github.com/ruby/ruby/pull/4372
|
|
Not all preprocessors work with output option.
Notes:
Merged: https://github.com/ruby/ruby/pull/4372
|
|
As it is an independent feature from `clz`, `ctz` and `popcount`,
it might be unavailable even if the latters are built in.
Notes:
Merged: https://github.com/ruby/ruby/pull/4372
|
|
|
|
|
|
|
|
As it is overridden by the definition in common.mk, instead define
YEAR, MONTH and DAY which are used there.
This macro is useful for daily build&installation by the
combination with "relative-load", for example:
```sh
$ ./configure --prefix=/. --enable-load-relative \
--with-destdir='$(HOME)/.rbenv/versions/$(RUBY_RELEASE_DATE)'
```
This can install images usable by rbenv per days.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4374
|
|
|
|
If a block is given, it returns a lazy enumerator that will iterate
over the block, it doesn't iterate over the block immediately.
Fixes [Bug #17789]
|
|
... the following timeout failure.
http://rubyci.s3.amazonaws.com/rhel_zlinux/ruby-master/log/20210408T213303Z.fail.html.gz
```
[ 8871/21204] TestGCCompact#test_ast_compactstimeout: output interval exceeds 600.0 seconds.
timeout: the process group 28416 is alive.
PSOUT PGID PID ELAPSED %CPU VSZ COMMAND COMMAND
PSOUT 28416 28416 12:46 0.0 108120 gmake gmake TESTS=--hide-skip -v RUBYOPT=-w test-all
PSOUT 28416 28423 12:46 88.2 1446124 ruby ./test/runner.rb: TestGCCompact#test_ast_compacts
timeout: INT signal sent.
timeout: INT signal sent.
timeout: TERM signal sent.
timeout: TERM signal sent.
timeout: KILL signal sent.
```
This error repeatedly occurs on RHEL s390x.
This change sends SEGV when timeout occurs so that it should dump the backtrace.
|
|
#reset, which is forgot to call
|
|
|
|
The kill/terminate interrupts are internally handled not as Exception
instances, but as integers. So using Exception doesn't handle these
interrupts, but Object does. You can use Integer if you only want to
handle kill/terminate interrupts, but that's probably more of an
implementation detail, while handling Object should work regardless
of the implementation.
Fixes [Bug #15735]
|
|
|
|
As expressions in a gemspec file are evaluated at the build time,
but not the run time, the conditional in the gemspec will not work
as intended.
https://github.com/ruby/reline/commit/c09b7c454a
|
|
https://github.com/ruby/reline/commit/ee23e6f3f8
|
|
https://github.com/ruby/reline/commit/27b689a7e2
|
|
As expressions in a gemspec file are evaluated at the build time,
but not the run time, the conditional in the gemspec will not work
as intended.
https://github.com/ruby/irb/commit/42f364ea23
|
|
And the required ruby version is 2.5 or later.
https://github.com/ruby/irb/commit/ac496d4c78
|
|
|
|
Seems like the test `TestZlibGzipFile#test_gzip_reader_zcat` fails when
the timestamp has `\n\n`.
https://ci.appveyor.com/project/ruby/ruby/builds/38597932
```
1) Error:
TestZlibGzipFile#test_gzip_reader_zcat:
Zlib::DataError: invalid distance too far back
C:/projects/ruby/test/zlib/test_zlib.rb:522:in `initialize'
C:/projects/ruby/test/zlib/test_zlib.rb:522:in `new'
C:/projects/ruby/test/zlib/test_zlib.rb:522:in `zcat'
C:/projects/ruby/test/zlib/test_zlib.rb:522:in `block (2 levels) in test_gzip_reader_zcat'
C:/projects/ruby/test/zlib/test_zlib.rb:521:in `open'
C:/projects/ruby/test/zlib/test_zlib.rb:521:in `block in test_gzip_reader_zcat'
C:/projects/ruby/lib/tempfile.rb:358:in `create'
C:/projects/ruby/test/zlib/test_zlib.rb:510:in `test_gzip_reader_zcat'
```
The test time is around 2021-04-08 04:40 +0900. Maybe the following time
should trigger the bug.
```
irb(main):001:0> Time.at(1617824266)
=> 2021-04-08 04:37:46 +0900
irb(main):002:0> [1617824266].pack("V")
=> "\n\nn`"
```
|
|
This avoid shelling out, and includes a narrower list of files.
https://github.com/ruby/optparse/commit/f3ca83caff
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
https://github.com/ruby/optparse/commit/d55d9284c3
|
|
https://github.com/ruby/optparse/commit/5618eeb49e
|
|
* More on tutorial: clearer example output
https://github.com/ruby/optparse/commit/84dfd92d2a
|
|
This gem exposes no executable files.
https://github.com/ruby/optparse/commit/d14bf83007
|
|
https://github.com/ruby/optparse/commit/f209276f79
|
|
If no files to be ignored, resetting with no argument means
resetting the whole directory.
|