- 17 Dec, 2019 3 commits
-
-
Yukihiro "Matz" Matsumoto authored
Refine output of `mrb_print_error()`
-
Yukihiro "Matz" Matsumoto authored
-
KOBAYASHI Shuji authored
The following improvements are made according to Ruby's behavior: - Match location number to index. - Remove duplicate most recent call output. - Fix that first call is not output when array (unpacked) backtrace. ### Example ```ruby def a; raise "error!" end def b; a end begin b rescue => e e.backtrace if ARGV[0] == "unpack" # unpack backtrace raise e end ``` #### Before this patch: ``` $ bin/mruby example.rb unpack trace (most recent call last): [0] example.rb:2:in b [1] example.rb:1:in a example.rb:1: error! (RuntimeError) ``` #### After this patch: ``` $ bin/mruby example.rb unpack trace (most recent call last): [2] example.rb:4 [1] example.rb:2:in b example.rb:1:in a: error! (RuntimeError) ```
-
- 16 Dec, 2019 6 commits
-
-
Yukihiro "Matz" Matsumoto authored
Fix mruby-io test for mingw32
-
Yukihiro "Matz" Matsumoto authored
Merge pull request #4878 from shuujii/remove-unneeded-null-checks-to-struct-backtrace_locationfilename Remove unneeded null checks to `struct backtrace_location::filename`
-
KOBAYASHI Shuji authored
`struct backtrace_location` is created only in `each_backtrace()`, and the `filename` field will never be null (it will be `(unknown)` if null).
-
Yukihiro "Matz" Matsumoto authored
Remove module only methods from class
-
Yukihiro "Matz" Matsumoto authored
Drop dependencies from `mruby-complex` to some gems
-
Yukihiro "Matz" Matsumoto authored
Add "mruby developers" into some gems; Resolve #4709
-
- 15 Dec, 2019 1 commit
-
-
KOBAYASHI Shuji authored
-
- 14 Dec, 2019 2 commits
- 13 Dec, 2019 2 commits
-
-
Yukihiro "Matz" Matsumoto authored
Fix arguments check to `Array#each`
-
KOBAYASHI Shuji authored
#### Before this patch: ``` $ mruby -e '[].each(1){}' #=> no error ``` #### After this patch: ``` $ mruby -e '[].each(1){}' #=> ArgumentError: wrong number of arguments ```
-
- 12 Dec, 2019 1 commit
-
-
Yukihiro "Matz" Matsumoto authored
Merge pull request #4861 from shuujii/fix-behavior-of-Kernel-Integer-to-numbers-ending-with-_-and-spaces Fix behavior of `Kernel#Integer` to numbers ending with `_` and spaces
-
- 11 Dec, 2019 1 commit
-
-
KOBAYASHI Shuji authored
#### Before this patch: ```ruby Integer("1_ ") #=> 1 ``` #### After this patch (same as Ruby): ```ruby Integer("1_ ") #=> ArgumentError ```
-
- 10 Dec, 2019 3 commits
-
-
Yukihiro "Matz" Matsumoto authored
Merge pull request #4860 from shuujii/fix-behavior-of-String-to_i-Kernel-Integer-to-numbers-starting-with-_ Fix behavior of `String#to_i`/`Kernel#Integer` to numbers starting with `_`
-
KOBAYASHI Shuji authored
#### Before this patch: ```ruby Integer("_1") #=> 1 "_1".to_i #=> 1 ``` #### After this patch (same as Ruby): ```ruby Integer("_1") #=> ArgumentError "_1".to_i #=> 0 ```
-
Yukihiro "Matz" Matsumoto authored
Merge pull request #4858 from shuujii/fix-that-String-to_f-accepts-consecutive-_-as-a-numeric-expression Fix that `String#to_f` accepts consecutive `_` as a numeric expression
-
- 09 Dec, 2019 8 commits
-
-
dearblue authored
It is writing side by side with the original authors.
-
KOBAYASHI Shuji authored
Consecutive `_` is not allowed as a numeric expression: 1_2__3 #=> SyntaxError Float("1_2__3") #=> ArgumentError Integer("1_2__3") #=> ArgumentError "1_2__3".to_i #=> 12 But `String#to_f` accept it, so I fixed the issue. Before this patch: "1_2__3".to_f #=> 123 After this patch: "1_2__3".to_f #=> 12
-
Yukihiro "Matz" Matsumoto authored
-
Yukihiro "Matz" Matsumoto authored
-
Yukihiro "Matz" Matsumoto authored
Now identifiers like `_1abc` are allowed.
-
Yukihiro "Matz" Matsumoto authored
-
Ukrainskiy Sergey authored
-
Yukihiro "Matz" Matsumoto authored
Fix keyword arguments not be obtained with `mrb_get_args()`; Fix #4754
-
- 08 Dec, 2019 3 commits
-
-
Yukihiro "Matz" Matsumoto authored
Fix the error message of `Kernel#Float`
-
KOBAYASHI Shuji authored
#### Before this patch: ``` $ bin/mruby -e 'Float("1_a")' -e:1: invalid string for float(a) (ArgumentError) ``` #### After this patch: ``` $ bin/mruby -e 'Float("1_a")' -e:1: invalid string for float("1_a") (ArgumentError) ```
-
Yukihiro "Matz" Matsumoto authored
Add tests to `Math`
-
- 07 Dec, 2019 2 commits
-
-
dearblue authored
If ":" is after "|" and there is no "?" or "*", the keyword argument could not be obtained and it was not initialized with `undef`. For example: "|oo:"
-
KOBAYASHI Shuji authored
-
- 05 Dec, 2019 3 commits
-
-
Yukihiro "Matz" Matsumoto authored
Auto detect `MRB_TIME_T_UINT`
-
KOBAYASHI Shuji authored
-
Yukihiro "Matz" Matsumoto authored
Refine `mrb_alloca()`
-
- 04 Dec, 2019 1 commit
-
-
KOBAYASHI Shuji authored
* The allocated memory is guaranteed to be aligned for any data type (it was not guaranteed when string type is embed). * Make allocation size exactly specified size (does not allocate space for a null byte).
-
- 03 Dec, 2019 3 commits
-
-
Yukihiro "Matz" Matsumoto authored
Silence Clang warning with `MRB_INT64` and `MRB_32BIT` in `time.c`
-
KOBAYASHI Shuji authored
Silence the following warnings: ``` /mruby/mrbgems/mruby-time/src/time.c:871:15: warning: result of comparison of constant 9223372036854775807 with expression of type 'time_t' (aka 'long') is always false [-Wtautological-constant-out-of-range-compare] if (tm->sec > MRB_INT_MAX || tm->sec < MRB_INT_MIN) { ~~~~~~~ ^ ~~~~~~~~~~~ /mruby/mrbgems/mruby-time/src/time.c:871:40: warning: result of comparison of constant -9223372036854775808 with expression of type 'time_t' (aka 'long') is always false [-Wtautological-constant-out-of-range-compare] if (tm->sec > MRB_INT_MAX || tm->sec < MRB_INT_MIN) { ~~~~~~~ ^ ~~~~~~~~~~~ /mruby/mrbgems/mruby-time/src/time.c:887:16: warning: result of comparison of constant 9223372036854775807 with expression of type 'time_t' (aka 'long') is always false [-Wtautological-constant-out-of-range-compare] if (tm->usec > MRB_INT_MAX || tm->usec < MRB_INT_MIN) { ~~~~~~~~ ^ ~~~~~~~~~~~ /mruby/mrbgems/mruby-time/src/time.c:887:42: warning: result of comparison of constant -9223372036854775808 with expression of type 'time_t' (aka 'long') is always false [-Wtautological-constant-out-of-range-compare] if (tm->usec > MRB_INT_MAX || tm->usec < MRB_INT_MIN) { ~~~~~~~~ ^ ~~~~~~~~~~~ ```
-
Yukihiro "Matz" Matsumoto authored
Silence Clang warning with `MRB_INT32` and `MRB_64BIT` in `time.c`
-
- 02 Dec, 2019 1 commit
-
-
KOBAYASHI Shuji authored
Silence the following warning: ``` /mruby/mrbgems/mruby-time/src/time.c:258:60: warning: result of comparison of constant -9223372036854775808 with expression of type 'mrb_int' (aka 'int') is always false [-Wtautological-constant-out-of-range-compare] if ((mrb_time_int)i > MRB_TIME_MAX || MRB_TIME_MIN > i) { ~~~~~~~~~~~~ ^ ~ ```
-