Yes, this could very well turn into a "dynamic vs. static" debate,
but I don't want it to.
--- SystemExit from thread: main
undefined method `each' for false:FalseClass
/Users/ari/local//lib/ruby/gems/1.8/gems/sup-0.5/lib/sup.rb:64:in
`select'
/Users/ari/local//lib/ruby/gems/1.8/gems/sup-0.5/lib/sup/buffer.rb:
31:in `nonblocking_getch'
/Users/ari/local//lib/ruby/gems/1.8/gems/sup-0.5/bin/sup:227
/Users/ari/local/lib/ruby/gems/1.8/bin/sup:19:in `load'
/Users/ari/local/lib/ruby/gems/1.8/bin/sup:19
I get way too many of these. Maybe it's because I'm using gmail and
it just gets sooooooo many hits that some get lost, but I'm tired of
it. I want to switch over to sup full-time, but I can't because it
crashes often, when I scroll down too much or when it tries to load a
lot of emails.
So... Is this some other problem, or should I go through and add a
bunch of "unless type === Something" throughout the code?
Option two.... Add NilClass#coerce
Is it worth doing this? I'm going to fix this either way, so the
question is.... Which will impact performance the least? Ruby is
interpreted so I don't have to worry about screwing up branch
prediction, but I'm worried about method calls.
Mr. Morgan, any advice for which path I should take?
Thanks,
-------------------------------------------------------|
~ Ari
".. NOT INTENDED FOR USE IN ... NUCLEAR FACILITIES, AIRCRAFT
NAVIGATION ... LIFE SUPPORT MACHINES" - iTunes EULA
_______________________________________________
sup-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/sup-talk
