From: fedzor@gmail.com (fedzor)
Subject: [sup-talk] Checking for unexpected types
Date: Wed, 4 Jun 2008 14:26:17 -0400 [thread overview]
Message-ID: <2747A2E5-4957-45B5-AC5F-605A3196F874@gmail.com> (raw)
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
next reply other threads:[~2008-06-04 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 18:26 fedzor [this message]
2008-06-04 19:12 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2747A2E5-4957-45B5-AC5F-605A3196F874@gmail.com \
--to=fedzor@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox