summaryrefslogtreecommitdiff
path: root/rational.c
Commit message (Collapse)AuthorAgeFilesLines
* [Feature #19474] Refactor NEWOBJ macrosMatt Valentine-House2023-04-061-1/+2
| | | | NEWOBJ_OF is now our canonical newobj macro. It takes an optional ec
* [DOC] Enhanced RDoc for NilClass (#7500)Burdette Lamar2023-03-131-5/+12
|
* Remove (newly unneeded) remarks about aliasesBurdetteLamar2023-02-191-1/+0
|
* Using UNDEF_P macroS-H-GAMELINKS2022-11-161-5/+5
|
* Improve performance some `Integer` and `Float` methods [Feature #19085] (#6638)S.H2022-10-271-27/+0
| | | | | | | * Improve some Integer and Float methods * Using alias and Remove unnecessary code * Remove commentout code
* Expand tabs [ci skip]Takashi Kokubun2022-07-211-373/+373
| | | | [Misc #18891]
* Disable GMP by -DUSE_GMP=0Nobuyoshi Nakada2022-05-201-3/+9
|
* [DOC] Fix broken links to literals.rdocNobuyoshi Nakada2022-02-081-1/+1
|
* [DOC] Simplify links to global methodsNobuyoshi Nakada2022-02-081-1/+1
|
* Adding links to literals and Kernel (#5192)Burdette Lamar2021-12-031-4/+10
| | | | * Adding links to literals and Kernel
* Using RB_BIGNUM_TYPE_P macroS-H-GAMELINKS2021-09-111-3/+3
|
* Make internal predicate functions to return simple booleanNobuyoshi Nakada2021-09-021-1/+1
|
* Remove unneeded comments in rational.cS-H-GAMELINKS2021-08-311-4/+0
|
* Use C99-defined macros to classify a floating-point numberNobuyoshi Nakada2021-08-271-2/+2
|
* Replace f_boolcast with RBOOL macroS.H2021-08-181-6/+5
| | | | | | | * Move f_boolcast definination * Remove f_boolcast macro defination * to
* Use Rational for Float#round with ndigits > 14Jeremy Evans2021-08-061-0/+6
| | | | | | | | | | | ndigits higher than 14 can result in values that are slightly too large due to floating point limitations. Converting to rational for the calculation and then back to float fixes these issues. Fixes [Bug #14635] Fixes [Bug #17183] Co-authored by: Yusuke Endoh <mame@ruby-lang.org>
* Use predefined IDsNobuyoshi Nakada2021-07-271-2/+2
|
* cdhash_cmp: can take rational literals卜部昌平2021-05-121-3/+10
| | | | | | | Rational literals are those integers suffixed with `r`. They tend to be a part of more complex expressions like `123/456r`, but in theory they can live alone. When such "bare" rational literals are passed to case-when branch, we have to take care of them. Fixes [Bug #17854]
* Rationalize floats in coerce [Bug #17572]Nobuyoshi Nakada2021-01-231-5/+11
|
* Make reciprocal properly of non-integral rational [Bug #17572]Nobuyoshi Nakada2021-01-231-1/+1
|
* Follow the NDEBUG given to the wholeNobuyoshi Nakada2021-01-071-2/+0
|
* Fix ArithmeticSequence#last and ArithmeticSequence#each for non-integer ↵Kenta Murata2020-12-091-8/+20
| | | | | | sequences (#3870) [Bug #17218] [ruby-core:100312]
* Removed canonicalization for mathnNobuyoshi Nakada2020-11-101-32/+3
|
* rational.c: convert a numerator to rational before calling fdiv in ↵Kenta Murata2020-10-261-1/+9
| | | | | | Kernel.Rational() (#3702) This makes `Rational(BigDecimal(1), 60) == Rational(1, 60)`. [Bug #16518]
* rational.c: try converting by to_int in Rational() (#3684)Kenta Murata2020-10-221-3/+31
| | | [Bug #12485]
* Don't redefine #rb_intern over and over againStefan Stüben2020-10-211-7/+4
|
* RARRAY_AREF: convert into an inline function卜部昌平2020-08-151-0/+1
| | | | | | RARRAY_AREF has been a macro for reasons. We might not be able to change that for public APIs, but why not relax the situation internally to make it an inline function.
* Reduced working `Rational` object allocationsNobuyoshi Nakada2020-07-011-15/+28
| | | | When rationalizing negative values.
* Renamed `nurat_sub` compliant with `rb_rational_plus`Nobuyoshi Nakada2020-07-011-3/+3
|
* Added a few integer case short-circuitsNobuyoshi Nakada2020-07-011-1/+9
|
* Replaced f_odd_p with rb_int_odd_pNobuyoshi Nakada2020-07-011-10/+1
|
* parse_rat: do not goto into a branch卜部昌平2020-06-291-12/+15
| | | | | I'm not necessarily against every goto in general, but jumping into a branch is definitely a bad idea. Better refactor.
* rb_rational_cmp: do not goto into a branch卜部昌平2020-06-291-10/+11
| | | | | I'm not necessarily against every goto in general, but jumping into a branch is definitely a bad idea. Better refactor.
* sed -i 's|ruby/impl|ruby/internal|'卜部昌平2020-05-111-1/+1
| | | | To fix build failures.
* sed -i s|ruby/3|ruby/impl|g卜部昌平2020-05-111-1/+1
| | | | This shall fix compile errors.
* reroute redefinition of NDEBUG卜部昌平2020-04-211-0/+1
| | | | | NDEBUG can be defined via a command-line argument. Should take care of such situations.
* Merge pull request #2991 from shyouhei/ruby.h卜部昌平2020-04-081-3/+2
| | | Split ruby.h
* rb_rational_raw: convert num and den by to_intKenta Murata2020-01-171-0/+4
|
* rb_rational_raw: make a denominator always positiveKenta Murata2020-01-171-0/+4
|
* internal/rational.h: insert assertions in RATIONAL_SET_{NUM,DEN}Kenta Murata2020-01-171-1/+0
|
* rational.c: remove nurat_s_newKenta Murata2020-01-171-33/+13
|
* Make RATIONAL_SET_{NUM,DEN} static inline functionsKenta Murata2020-01-171-4/+4
|
* decouple internal.h headers卜部昌平2019-12-261-8/+15
| | | | | | | | | | | | | | | | | | Saves comitters' daily life by avoid #include-ing everything from internal.h to make each file do so instead. This would significantly speed up incremental builds. We take the following inclusion order in this changeset: 1. "ruby/config.h", where _GNU_SOURCE is defined (must be the very first thing among everything). 2. RUBY_EXTCONF_H if any. 3. Standard C headers, sorted alphabetically. 4. Other system headers, maybe guarded by #ifdef 5. Everything else, sorted alphabetically. Exceptions are those win32-related headers, which tend not be self- containing (headers have inclusion order dependencies).
* Deprecate taint/trust and related methods, and make the methods no-opsJeremy Evans2019-11-181-1/+0
| | | | | | 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.
* Make rb_scan_args handle keywords more similar to Ruby methods (#2460)Jeremy Evans2019-09-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cfuncs that use rb_scan_args with the : entry suffer similar keyword argument separation issues that Ruby methods suffer if the cfuncs accept optional or variable arguments. This makes the following changes to : handling. * Treats as **kw, prompting keyword argument separation warnings if called with a positional hash. * Do not look for an option hash if empty keywords are provided. For backwards compatibility, treat an empty keyword splat as a empty mandatory positional hash argument, but emit a a warning, as this behavior will be removed in Ruby 3. The argument number check needs to be moved lower so it can correctly handle an empty positional argument being added. * If the last argument is nil and it is necessary to treat it as an option hash in order to make sure all arguments are processed, continue to treat the last argument as the option hash. Emit a warning in this case, as this behavior will be removed in Ruby 3. * If splitting the keyword hash into two hashes, issue a warning, as we will not be splitting hashes in Ruby 3. * If the keyword argument is required to fill a mandatory positional argument, continue to do so, but emit a warning as this behavior will be going away in Ruby 3. * If keyword arguments are provided and the last argument is not a hash, that indicates something wrong. This can happen if a cfunc is calling rb_scan_args multiple times, and providing arguments that were not passed to it from Ruby. Callers need to switch to the new rb_scan_args_kw function, which allows passing of whether keywords were provided. This commit fixes all warnings caused by the changes above. It switches some function calls to *_kw versions with appropriate kw_splat flags. If delegating arguments, RB_PASS_CALLED_KEYWORDS is used. If creating new arguments, RB_PASS_KEYWORDS is used if the last argument is a hash to be treated as keywords. In open_key_args in io.c, use rb_scan_args_kw. In this case, the arguments provided come from another C function, not Ruby. The last argument may or may not be a hash, so we can't set keyword argument mode. However, if it is a hash, we don't want to warn when treating it as keywords. In Ruby files, make sure to appropriately use keyword splats or literal keywords when calling Cfuncs that now issue keyword argument separation warnings through rb_scan_args. Also, make sure not to pass nil in place of an option hash. Work around Kernel#warn warnings due to problems in the Rubygems override of the method. There is an open pull request to fix these issues in Rubygems, but part of the Rubygems tests for their override fail on ruby-head due to rb_scan_args not recognizing empty keyword splats, which this commit fixes. Implementation wise, adding rb_scan_args_kw is kind of a pain, because rb_scan_args takes a variable number of arguments. In order to not duplicate all the code, the function internals need to be split into two functions taking a va_list, and to avoid passing in a ton of arguments, a single struct argument is used to handle the variables previously local to the function.
* rb_numeric_quo: support ComplexNobuyoshi Nakada2019-08-101-0/+4
|
* Predefine some IDsNobuyoshi Nakada2019-08-031-4/+5
|
* Make float_decode_internal mantissa intNobuyoshi Nakada2019-08-021-21/+17
|
* Deduplicate common codeNobuyoshi Nakada2019-08-021-13/+5
|
* Expanded f_quoNobuyoshi Nakada2019-08-021-1/+10
|
View Lorry Controller Status