public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Quentin Barnes <qbarnes@urbana.css.mot.com>
To: Roland McGrath <roland@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: ARM port of testsuite and general testsuite fixes
Date: Wed, 06 Jun 2007 23:44:00 -0000	[thread overview]
Message-ID: <20070606234357.GH20115@urbana.css.mot.com> (raw)
In-Reply-To: <20070606231008.91DD34D0592@magilla.localdomain>

>The difference in tcl between {foo bar} and {foo\ bar} is whether as a list
>it's considered two elements or one, so that might be the issue.

I don't know the nuances of the TCL language.  In the grammar, do
brackets always define a list, or only when the preceding keyword
is syntactically expecting a list to follow?


If whitespace is being parsed as a list separator, I would expect
these two statements to be equivalent:
        -re {^hi there} ...
and:
        -re {^hi     there} ...

But they are not.

I couldn't come up with a test case where escaping the space made
any actual difference.  (Just conceptual difference?)  Is there a
subtle case where the distinction matters?

Quentin

  reply	other threads:[~2007-06-06 23:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06  0:36 Quentin Barnes
2007-06-06 16:02 ` David Smith
2007-06-06 17:11   ` Quentin Barnes
2007-06-06 18:22     ` David Smith
2007-06-06 18:39       ` Martin Hunt
2007-06-06 19:25       ` Quentin Barnes
2007-06-06 19:51         ` David Smith
2007-06-06 20:00           ` Quentin Barnes
2007-06-06 20:07             ` David Smith
2007-06-06 20:39               ` Quentin Barnes
2007-06-06 21:01                 ` David Smith
2007-06-06 21:35                   ` Quentin Barnes
2007-06-06 21:51                     ` David Smith
2007-06-06 23:10                       ` Roland McGrath
2007-06-06 23:44                         ` Quentin Barnes [this message]
2007-06-07  1:05                           ` Roland McGrath
2007-06-08 16:27 ` Quentin Barnes

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=20070606234357.GH20115@urbana.css.mot.com \
    --to=qbarnes@urbana.css.mot.com \
    --cc=roland@redhat.com \
    --cc=systemtap@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).