charlton (Charlton Wang)
- Login: charlton
- Email: charlton.wang@gmail.com
- Registered on: 07/24/2009
- Last sign in: 04/18/2015
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 3 | 3 |
Activity
04/18/2015
-
05:39 AM Ruby Bug #11074 (Rejected): Block with optional parameter of same closure variable name
- ~~~ruby
def bar
yield
end
x = 3
bar do |x=x|
x
end
=> nil
bar do |y=x|
x
end
=> 3
~~~
So perhaps `x=x` isn't able to distinguish that the RHS should probably be the closure `x` and, instead, is take to mean the value...
02/02/2012
-
- Yusuke Endoh wrote:
> Do you really like the old behavior? Line 8 points
> ...
I think the old behaviour will point you to the first line *after* the do. I agree that line 7 would be better but at least line 8 is deterministic so eith...
01/26/2012
-
- I've verified this behaviour under the following versions:
works: ruby 1.9.1p243 (2009-07-16 revision 24175) [i386-darwin10.4.0]
fails: ruby 1.9.2p136 (2010-12-25 revision 30365) [x86_64-darwin10.4.0]
fails: ruby 2.0.0dev (2012-01-26 tr... -
- Similar to bug #2427 but maybe the opposite problem. Newer versions of ruby appear to store the source locations of blocks incorrectly when passed as an argument to a multi-line invocation of a function. Snippet of code below reveals the...
07/22/2011
-
- Is there any hope of getting __callee__ functionality back at some point? I tried to write a ruby extension that provided a function to call what used to be called by __callee__ but that doesn't appear to work. Has the VM changed to the ...
07/24/2009
-
- =begin
I should have realized that the 1.9 series uses native threads and I suspect that's likely the cause (presumably a stack size limitation?).
=end
-
- =begin
I'm not sure if there is a thread stack limitation change that is new to 1.9.1 but the following code now causes a segfault on Linux and Illegal Instruction on the Mac. I know this code is somewhat ridiculous (call stack is atte...