>If you want the same behavior, you need to use parentheses: > ... # ok, but also with ((...)) [most people] would assume its meaning is (x, y=x+1, y+1)... *Other example: p(x+=1,x+=1) # ok p (x+=1,x+=1) # error p ((x,y)=[x+1,...opti (Andreas Opti)
output [time1,time2] of daysaving-changes of given year I assume the result does not depend on timezone, only the output will be in default timezone. opti (Andreas Opti)
Hi Its not nice to remove issues, I invested much time to test it, also with different Ruby-versions, so please at least tell me (maybe via Mail), why you deleted that issue. After having put it in the buglist, I deleted all my files ...opti (Andreas Opti)
x=y=0 # outside defined vars! 3.times { x,y = x+1,y+1 } # as expected: x==3 3.times { p(x,y = x+1,y+1) } # NOT as expected: x not changed! # x,y are the same vars as above. p shoudn't have any effect on scope opti (Andreas Opti)
x=y=0 # outside defined vars! 3.times {|i| x,y=x+1,y+1 } # as expected: x==3 3.times {|i| p(x,y=x+1,y+1) } # NOT as expected: x not changed! # x,y are the same vars as above. p shoudn't have any effect on scope opti (Andreas Opti)
If having (new) Dir.entries, Dir.chidren, I would also add: Dir.entries (includes all), Dir.files Dir.dirs Dir.symlinks Dir.pipes (Dir.something_more?) Dir.file?(filename); Dir.symlink[s]?(*symlinks), etc # give one or more names ...opti (Andreas Opti)
I didn't manage to compile Ruby v250 (because of other errrors), nice to see that this bug is fixed now. (I mentioned it in a mailinglist some months ago). Now I found in the changelog "r59074 | ko1 | 2017-06-13 11:52:33 +0900 (Tue, 13...opti (Andreas Opti)
100.times {x=[]; 1000000.times {|i| x.push [i,i*3]} } 100.times should use (more or less) the same memory as 3.times, also GC.start after x=[] doesn't help! Problem: system begins swapping if doing that many times (using large data a...opti (Andreas Opti)
opti (Andreas Opti)09:34 PM Ruby Bug #13815 (Open): p args