Excerpts from Wirt Wolff's message of Wed Aug 19 13:41:54 -0700 2009: > Lots of great improvements in next. Love the utf8.
Agreed. These are very nice.
> When I try to 'l'abel in thread view mode, however, sup crashes with
>
> --- NoMethodError from thread: main
> undefined method `join' for #<Set: {:list, :xm}>
> ./lib/sup/buffer.rb:506:in `ask_for_labels'
I'm getting that too. It bisected down to the following which is not
so surprising:
commit 7aea418a8a62b7070eee764475fcfc0bdd8d58dd
Author: William Morgan <[email protected]>
Date: Tue Aug 11 16:00:52 2009 -0400
maintain labels as Sets rather than arrays
I've attached a patch that at least makes the crashes I was able ro
reproduce go away. But I have no idea if I got them all of course[*].
And please let me know if I'm doing anything wrong. I'm new to ruby as
well as sup here, so go easy on me, please! :-)
-Carl
[*] Totally off-topic: This is one of the things about "dynamically
typed" languages that I've never been able to wrap my brain around. I
really like that with static typing I can trust the compiler to help
me be very thorough if I make a type change like this, (and catch all
the cases before shipping any code). Instead, here, there's a hard
task of exercising every possible code path (at run time) before we
know if there are any type errors still lingering. I've seen some
proponents of dynamically-typed languages argue that unit testing
should provide the same coverage that a statically-typed compiler
would, but I haven't seen that in practice.
You all definitely have a lot more experience with ruby than I do, so
I'm honestly interested in learning form your experience. What do you
do to deal with cases like this?
0001-Convert-a-couple-of-arrays-to-sets-for-labels.patch
Description: Binary data
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
