From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] [Bug#647226: edbrowse: button press does not...
Date: Wed, 02 Nov 2011 05:48:33 -0500 [thread overview]
Message-ID: <877h3ilrzy.fsf@the-brannons.com> (raw)
In-Reply-To: <20110931193027.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 31 Oct 2011 19:30:27 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> Here is what has confused me from the start.
> How to make javascript march on even if something is undefined.
The problem with just blindly marching on is that errors can cascade.
Have you ever seen a shell script fail because one of its component
commands is undefined? It just keeps trudging. Sometimes, it can get
pretty ugly, as failure begets failure. This is one of the numerous things
I dislike about shell scripting.
Your point is a good one, though, and it bares investigating. Maybe the
best approach is to go digging around in the firefox source. That's a
scary prospect, though.
-- Chris
prev parent reply other threads:[~2011-11-02 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 23:30 Karl Dahlke
2011-11-02 10:48 ` Chris Brannon [this message]
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=877h3ilrzy.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.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;
as well as URLs for NNTP newsgroup(s).