aboutsummaryrefslogtreecommitdiffstats
path: root/ext
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Update dependencies"Vít Ondruch2019-11-221-45/+0
| | | | | | | | This reverts commit e1b234148829f65bea9f5ecc7018beb782ea6023. This allows to build Psych against system libyaml again on Fedora. [Bug #16359]
* Check -1 arity for C++Nobuyoshi Nakada2019-11-223-5/+23
|
* Revert the line for nextafter.c for FreeBSD makeNobuyoshi Nakada2019-11-201-0/+3
|
* Configure static extensions only if in chargeNobuyoshi Nakada2019-11-191-1/+5
| | | | | Get rid of races in parallel configuration when using the ext/Setup file.
* Update dependenciesNobuyoshi Nakada2019-11-1816-91/+106
|
* [ruby/strscan] Remove taint supportJeremy Evans2019-11-181-16/+8
| | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions.
* [ruby/openssl] Remove taint supportJeremy Evans2019-11-183-11/+0
| | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions.
* [ruby/io-console] Remove taint supportJeremy Evans2019-11-181-1/+0
| | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions.
* [ruby/etc] Remove taint supportJeremy Evans2019-11-181-3/+4
| | | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. Still untaint the tmpdir object on Ruby <2.7, as returning a tainted string there could cause problems.
* Deprecate taint/trust and related methods, and make the methods no-opsJeremy Evans2019-11-1811-35/+24
| | | | | | This removes the related tests, and puts the related specs behind version guards. This affects all code in lib, including some libraries that may want to support older versions of Ruby.
* Warn on access/modify of $SAFE, and remove effects of modifying $SAFEJeremy Evans2019-11-1811-39/+2
| | | | | | | | | | | | | | | | | This removes the security features added by $SAFE = 1, and warns for access or modification of $SAFE from Ruby-level, as well as warning when calling all public C functions related to $SAFE. This modifies some internal functions that took a safe level argument to no longer take the argument. rb_require_safe now warns, rb_require_string has been added as a version that takes a VALUE and does not warn. One public C function that still takes a safe level argument and that this doesn't warn for is rb_eval_cmd. We may want to consider adding an alternative method that does not take a safe level argument, and warn for rb_eval_cmd.
* Update comment of Ripper.lexYuichiro Kaneko2019-11-131-10/+10
| | | | This is follow up of 1f7cb4bee9.
* Revert "Method reference operator"Nobuyoshi Nakada2019-11-122-2/+0
| | | | | This reverts commit 67c574736912003c377218153f9d3b9c0c96a17b. [Feature #16275]
* [ruby/bigdecimal] Remove taint checkingJeremy Evans2019-11-121-3/+0
| | | | | | | | This removes the taint checking. Taint support is deprecated in Ruby 2.7 and has no effect. I don't think removing the taint checks in earlier ruby versions will cause any problems. https://github.com/ruby/bigdecimal/commit/1918d466f3
* [ruby/psych] Add a note about safe_loadAaron Patterson2019-11-121-0/+4
| | | | https://github.com/ruby/psych/commit/0910ae5575
* [ruby/psych] Remove taint supportJeremy Evans2019-11-122-20/+2
| | | | | | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. I'm not sure if the untaint calls in deduplicate are still needed after the removal of tainting in the parser. If they are not needed, they should be removed. https://github.com/ruby/psych/commit/73c1a2b4e0
* [ruby/psych] Set required_ruby_version to 2.4.0Jean Boussier2019-11-121-1/+1
| | | | https://github.com/ruby/psych/commit/4f1746a3c6
* Monitor#exit: check monitor ownership.Koichi Sasada2019-11-121-10/+15
| | | | | Monitor#exit should be called by only onwer Thread. However, there is not check for it.
* Removed duplicate fileNobuyoshi Nakada2019-11-111-2/+109
| | | | | "./tests/test_helper.rb" and "tests/test_helper.rb" in `s.files` are same.
* Remove unneeded exec bits from some filesDavid Rodríguez2019-11-097-0/+0
| | | | | | | | | | | | | I noticed that some files in rubygems were executable, and I could think of no reason why they should be. In general, I think ruby files should never have the executable bit set unless they include a shebang, so I run the following command over the whole repo: ```bash find . -name '*.rb' -type f -executable -exec bash -c 'grep -L "^#!" $1 || chmod -x $1' _ {} \; ```
* Promote readline to default gems named readline-extHiroshi SHIBATA2019-11-091-0/+21
|
* Suppress unused variable warningNobuyoshi Nakada2019-11-071-1/+1
|
* Adjust a fucntion signatureNobuyoshi Nakada2019-11-051-2/+8
|
* Clean up implementation of SOCKSSocket, its confusing and undocumentedJustin McNally2019-11-011-4/+10
|
* Prefer libsocksd over libsocksJustin McNally2019-11-011-1/+1
|
* Support libsocksd socks library for SOCKSSocketJustin McNally2019-11-011-1/+1
|
* [ruby/date] Added update-zonetab targetNobuyoshi Nakada2019-11-012-0/+39
| | | | https://github.com/ruby/date/commit/9bc6e30a82
* [ruby/date] Add more timezone abbreviationsJeremy Evans2019-11-012-689/+1460
| | | | | | | | | | | | | | | | This gets the time zone abbreviations from https://www.timeanddate.com/time/zones/, and adds unambiguous time zones not already present in zonetab.list. See bin/update-abbr for the program used. This regenerates zonetab.h using prereq.mk (requires gperf). Only one test line is added, just to make sure a new time zone abbreviation is picked up. Fixes Ruby Bug 16286 https://github.com/ruby/date/commit/702e8b3033
* [ruby/zlib] Removed no longer used variablesNobuyoshi Nakada2019-10-311-2/+1
| | | | https://github.com/ruby/zlib/commit/3e98e4cac3
* [ruby/zlib] Fix setting mtime to zero in GzipWriterAlan Wu2019-10-311-1/+3
| | | | | | | | | | | Before this change, it was not possible to write out zero for the timestamp part of a Gzip file's header, as calling GzipWriter#mtime with zero was ignored. Judging from the docs for `GzipWriter#mtime=`, it should be possible to indicate that no timestamp is available by calling the method with zero. https://github.com/ruby/zlib/commit/310be39cac
* [ruby/stringio] Remove taint supportJeremy Evans2019-10-311-4/+0
| | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. https://github.com/ruby/stringio/commit/60ee9ccd95
* [ruby/date] Revert "Simplify #inspect"Jeremy Evans2019-10-311-2/+5
| | | | | | | | This reverts commit af01edd7d8575f544f647dbe8cde5b6ae535d459. Revert requested by Yui Naruse. https://github.com/ruby/date/commit/875d563557
* [ruby/date] introduce Date::Error, raise Date::Error for everyglaszig2019-10-311-30/+32
| | | | | | "invalid <anything>" type of exception https://github.com/ruby/date/commit/3e55c09ba4
* [ruby/gdbm] Use Gemfile instead of ↵Hiroshi SHIBATA2019-10-311-5/+0
| | | | | | Gem::Specification#add_development_dependency. https://github.com/ruby/gdbm/commit/bd2e7f6647
* [ruby/gdbm] Remove taint supportJeremy Evans2019-10-311-3/+0
| | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. https://github.com/ruby/gdbm/commit/f9aaa1a08d
* [ruby/zlib] Remove taint supportJeremy Evans2019-10-311-35/+1
| | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. https://github.com/ruby/zlib/commit/21711ed0ce
* Update the latest versions from upstream repository of raccHiroshi SHIBATA2019-10-301-1/+1
|
* Update StringIO docs:zverok2019-10-261-41/+56
| | | | | | | | | | | * More explanations/examples in class docs; * Fix links to other methods (remove <code> tag); * Fix wording of method docs (remove *stringio* receiver name, as it is not rendered by modern RDoc); * Add option mention to linereading methods (added in 2.4); * Several other small fixes.
* [ruby/dbm] Remove taint supportJeremy Evans2019-10-261-22/+21
| | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. https://github.com/ruby/dbm/commit/1f0ff0bce1
* Fix typo causing Date.new(year, month) to failJeremy Evans2019-10-241-1/+1
| | | | Add a test for this case.
* Revert "[ruby/fiddle] Use ffi_closure_free by default. (#20)"Hiroshi SHIBATA2019-10-242-6/+42
| | | | This reverts commit ce6caade7c57a505f73086ccd7b33c14f7715f22.
* [ruby/fiddle] Remove taint support (#21)Jeremy Evans2019-10-243-21/+8
| | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous Ruby versions. https://github.com/ruby/fiddle/commit/18d6fb6915
* [ruby/fiddle] Use ffi_closure_free by default. (#20)Vít Ondruch2019-10-242-42/+6
| | | | | | | | | | | | | | | | | | | | | * Use ffi_closure_free unconditionally. The current conditionals reflect historic heritage of FFI. Usage of ffi_closure_free should be better default nowadays, because libffi 3.0.5 fixing issues of ffi_closure_free should be widely available. * RUBY_LIBFFI_MODVERSION is not used anymore. Because `ffi_closure_free()` is not used unconditionally, there is no other use for RUBY_LIBFFI_MODVERSION define, so drop its usage. * Use more meaningful variable name. `ver` variable used to be used to pupulate RUBY_LIBFFI_MODVERSION define. Since the define was removed, the `libffi_dir` variable name should better describe the remaining usage of the variable. https://github.com/ruby/fiddle/commit/c49cc79eb8
* [ruby/fiddle] Fiddle::Function must maintain a reference to the closureAaron Patterson2019-10-241-0/+2
| | | | | | | | | | | | If the first parameter to Fiddle::Function is a closure object (rather than an interger), `rb_Integer` will cast it to an integer but not maintain a reference to the closure. Then if the closure gets GC'd, we have a segv. This commit keeps a reference to the original parameter to initialize so that the object will not be GC'd. Fixes: https://bugs.ruby-lang.org/issues/13286 https://github.com/ruby/fiddle/commit/0fc697bbc5
* [ruby/date] Use Gemfile instead of ↵Hiroshi SHIBATA2019-10-241-2/+0
| | | | | | Gem::Specification#add_development_dependency. https://github.com/ruby/date/commit/13c94362c2
* [ruby/date] Update docszverok2019-10-241-2/+2
| | | | https://github.com/ruby/date/commit/8c02586a98
* [ruby/date] Simplify #inspectzverok2019-10-241-5/+2
| | | | https://github.com/ruby/date/commit/af01edd7d8
* [ruby/date] Remove taint supportJeremy Evans2019-10-241-7/+0
| | | | | | | | Ruby 2.7 deprecates taint and it no longer has an effect. The lack of taint support should not cause a problem in previous versions. https://github.com/ruby/date/commit/519470dc3b
* [ruby/date] Support -Float::INFINITY...date rangesJeremy Evans2019-10-241-0/+4
| | | | | | Fixes Ruby Bug 12961 https://github.com/ruby/date/commit/7f533c2552
* [ruby/date] Check for numeric arguments in constructorsJeremy Evans2019-10-241-0/+49
| | | | | | | | | | | | | | | Previously, the type of these arguments were not checked, leading to NoMethodErrors in some cases, and TypeErrors in other cases, but not showing what field was having the problems. This change makes it so the field with the problem is included in the error message. For the valid_*? methods, this changes them to return false if one of the arguments that should be numeric is not. Fixes Ruby Bug 11935 Fixes Ruby Misc 15298 https://github.com/ruby/date/commit/a2f4b665f8
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-24 05:58:57 +0000