From: jtc@redback.com (J.T. Conklin)
To: Stan Shebs <shebs@cygnus.com>
Cc: gdb@cygnus.com
Subject: Re: problem with chained if statements?
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <5m4snj4qv1.fsf@jtc.redbacknetworks.com> (raw)
In-Reply-To: <199903170011.QAA07805@andros.cygnus.com>
jtc> I'm trying to write some user-defined commands to traverse
jtc> and/or pretty-print some of the internal data structures used in
jtc> our SW. In the absense of a `switch' statement, I am using a
jtc> chain of if .. else if ... else if ... else ... end statements.
jtc> Unfortunately it doesn't seem to work.
Stan> Try:
Stan> if ($status == $TASK_READY)
Stan> printf "READY "
Stan> else
Stan> if ($status == $TASK_DELAY)
Stan> printf "DELAY "
Stan> else
Stan> if ($status == ($TASK_DELAY | $TASK_SUSPEND))
Stan> printf "DELAY+S "
Stan> I think the else and the if each need to be on their own lines.
It turns out to be something like:
if ($status == $TASK_READY)
printf "READY "
else
if ($status == $TASK_DELAY)
printf "DELAY "
else
if ($status == ($TASK_DELAY | $TASK_SUSPEND))
printf "DELAY+S "
else
....
end
end
end
Pretty ugly (IMO). It will suffice as a workaround, but I'll have to
look into how difficult adding "true" else-if support will be. Would
an `elif' keyword be objectionable? What are the current thoughts
wrt. adding a more capable extension language for gdb scripting?
--jtc
--
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 0:00 J.T. Conklin
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` J.T. Conklin [this message]
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 Thompson, James C
1999-04-01 0:00 Thompson, James C
1999-04-01 0:00 ` Ovidiu Predescu
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Todd Whitesel
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=5m4snj4qv1.fsf@jtc.redbacknetworks.com \
--to=jtc@redback.com \
--cc=gdb@cygnus.com \
--cc=shebs@cygnus.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