From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC PATCH] Add u-boot command regression tests.
Date: Wed, 28 Nov 2007 13:11:07 -0500 [thread overview]
Message-ID: <200711281311.08028.vapier@gentoo.org> (raw)
In-Reply-To: <474ACEEC.1080801@ge.com>
On Monday 26 November 2007, Jerry Van Baren wrote:
> My experience with expect is that it worked well for simple cases, but
> when I started matching more patterns and more complex patterns, it
> would get harder and harder to match reliably. Also, its asynchronous
> timing-based capture (which causes "capture breaks" in different places
> when you least expect it) drove me crazy. Then to debug the pattern
> matching (or not matching, or mismatching, as the case usually was) was
> difficult.
i think that's really nature of the beast and not a deficiency in expect. how
do you know when things stop coming in ? you dont ... so write properly
anchored input matches and things work nicely
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20071128/8dda484f/attachment.pgp
prev parent reply other threads:[~2007-11-28 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 1:03 [U-Boot-Users] [RFC PATCH] Add u-boot command regression tests Jerry Van Baren
2007-11-25 23:29 ` Wolfgang Denk
2007-11-26 13:49 ` Jerry Van Baren
2007-11-26 14:09 ` Wolfgang Denk
2007-11-27 22:46 ` Robert Schwebel
2007-11-28 2:32 ` gvb.uboot
2007-11-28 17:13 ` Robert Schwebel
2007-11-27 23:30 ` Kumar Gala
2007-11-28 0:58 ` gvb.uboot
2007-11-28 18:11 ` Mike Frysinger [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=200711281311.08028.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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