[#1579] arity bug? — "Christoph" <chr_news@...>
Hi,
5 messages
2003/10/05
[#1588] FreeBSD problem with processes — Laurent Sansonetti <pinux@...>
Hi all,
1 message
2003/10/07
[#1591] Re: Yielding to a block from a proc? — george.marrows@...
> > Is this right? Is this pathological? Is it a bug? Is there
6 messages
2003/10/08
[#1596] PATCH: Revive NextStep, OpenStep, Rhapsody ports — Eric Sunshine <sunshine@...>
Hello,
7 messages
2003/10/09
[#1597] Re: PATCH: Revive NextStep, OpenStep, Rhapsody ports
— matz@... (Yukihiro Matsumoto)
2003/10/09
Hi,
[#1600] CVS access — Sean Russell <ser@...>
Hiya,
8 messages
2003/10/09
[#1611] set_trace_func/Array#fetch error — "Nathaniel Talbott" <nathaniel@...>
I've reduced the error I reported in ruby-talk:84013 to the following code:
17 messages
2003/10/11
[#1612] Re: set_trace_func/Array#fetch error
— ts <decoux@...>
2003/10/11
>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:
[#1616] Re: set_trace_func/Array#fetch error
— "Nathaniel Talbott" <nathaniel@...>
2003/10/11
ts [mailto:decoux@moulon.inra.fr] wrote:
[#1617] Re: set_trace_func/Array#fetch error
— ts <decoux@...>
2003/10/11
>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:
[#1618] Re: set_trace_func/Array#fetch error
— "Nathaniel Talbott" <nathaniel@...>
2003/10/11
ts [mailto:decoux@moulon.inra.fr] wrote:
[#1634] stringy range bug — "Christoph" <chr_news@...>
Hi,
6 messages
2003/10/15
[#1640] SystemStackError in embedding — Sentinel <sentinel27@...>
Hi, I am just now trying to embed ruby into my apprication
8 messages
2003/10/18
Re: set_trace_func/Array#fetch error
From:
"daz" <dooby@...10.karoo.co.uk>
Date:
2003-10-12 15:02:32 UTC
List:
ruby-core #1624
>
> Unfortunately, I guess it doesn't solve the true problem. It's
> due to the bug that determining the local jump destination by
> ruby_scope. See the thread from [ruby-talk:83729].
>
> --
> Nobu Nakada
>
IMvvHO connecting these two problems would lead to complications.
The inject problem is real because it has 'break' in a valid context.
The optparse problem has 'return' in a questionable context
instead of doing something like:
def search ...
if ...
val = list.fetch(key) {:return_nil} # <---
return nil if val == :return_nil # <---
return val unless block_given?
yield(val)
end
end
(I assume here that list might contain keys having OK 'nil' values).
Clumsy - but it makes the point that we can code our way out of
rare difficulties or refactor them away.
The 'unexpected return' error message seems totally sensible
for the original optparse code.
The error below is, more obviously, also helpful:
def roo
break
end
roo
#-> C:/TEMP/rb8120.TMP:2:in `roo': unexpected break (LocalJumpError)
#-> from C:/TEMP/rb8120.TMP:5
I would fix it by replacing the break.
#-> C:/TEMP/rb8120.TMP:2:in `roo': unexpected redo (LocalJumpError)
#-> from C:/TEMP/rb8120.TMP:5
Oh dear. It's not my day. Please don't fix this, though.
daz
(I just saw a reply from Guy to your next message :-)))))