From: Christopher Faylor <cgf@cygnus.com>
To: dwsharp@iee.org, cygwin@sourceware.cygnus.com
Subject: Re: sources
Date: Tue, 16 Feb 1999 17:26:00 -0000 [thread overview]
Message-ID: <19990216202649.B16511@cygnus.com> (raw)
In-Reply-To: < 36C938C5.D367F910@dddandr.octacon.co.uk >; from Don Sharp on Tue, Feb 16, 1999 at 09:22:13AM +0000
On Tue, Feb 16, 1999 at 09:22:13AM +0000, Don Sharp wrote:
>> On Mon, Feb 15, 1999 at 05:17:39PM +0000, Don Sharp wrote:
>> >As Chris is in denial mode wrt ash I'll need to have a go at fixing the
>> >missing character problem in the pattern match. (He is right in saying
>> >that it isn't something that the Bourne shell can do anyway so what/who
>> >decides the correct behaviour is possibly a moot point).
>>
>> Denial mode? You want ash to handle the same substitutions as bash. It
>> isn't going to happen.
>
>It was perhaps unkind to tweak Chris' tail, but I would expect that if
>ash accepts an expression for evaluation, (one which the Bourne /bin/sh
>won't entertain), and the expression requests the longest possible
>string up to but not including the nominated terminating character, I
>don't expect to be delivered one character short. If the expression in
>ash has a completely different meaning than it does in bash then Chris
>is right. However he hasn't stated that the rule for interpreting the
>expression is different in ash and bash.
>
>So either the expression evaluation is incorrect or the syntax of the
>expressions is identical and their semantics are different. Which is
>it?
The expression evaluation is is incorrect in that it is actually parsed
by ash rather resulting in a "bad substitution" error. In the next
net release this problem will be rectified.
cgf
WARNING: multiple messages have this Message-ID
From: Christopher Faylor <cgf@cygnus.com>
To: dwsharp@iee.org, cygwin@sourceware.cygnus.com
Subject: Re: sources
Date: Sun, 28 Feb 1999 23:02:00 -0000 [thread overview]
Message-ID: <19990216202649.B16511@cygnus.com> (raw)
Message-ID: <19990228230200.viUjJCO82LRUnRnzW7GjIENe926FqxxGVNLEm8N28Kk@z> (raw)
In-Reply-To: <36C938C5.D367F910@dddandr.octacon.co.uk>
On Tue, Feb 16, 1999 at 09:22:13AM +0000, Don Sharp wrote:
>> On Mon, Feb 15, 1999 at 05:17:39PM +0000, Don Sharp wrote:
>> >As Chris is in denial mode wrt ash I'll need to have a go at fixing the
>> >missing character problem in the pattern match. (He is right in saying
>> >that it isn't something that the Bourne shell can do anyway so what/who
>> >decides the correct behaviour is possibly a moot point).
>>
>> Denial mode? You want ash to handle the same substitutions as bash. It
>> isn't going to happen.
>
>It was perhaps unkind to tweak Chris' tail, but I would expect that if
>ash accepts an expression for evaluation, (one which the Bourne /bin/sh
>won't entertain), and the expression requests the longest possible
>string up to but not including the nominated terminating character, I
>don't expect to be delivered one character short. If the expression in
>ash has a completely different meaning than it does in bash then Chris
>is right. However he hasn't stated that the rule for interpreting the
>expression is different in ash and bash.
>
>So either the expression evaluation is incorrect or the syntax of the
>expressions is identical and their semantics are different. Which is
>it?
The expression evaluation is is incorrect in that it is actually parsed
by ash rather resulting in a "bad substitution" error. In the next
net release this problem will be rectified.
cgf
next prev parent reply other threads:[~1999-02-16 17:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-16 1:31 sources Don Sharp
[not found] ` < 36C938C5.D367F910@dddandr.octacon.co.uk >
1999-02-16 17:26 ` Christopher Faylor [this message]
1999-02-28 23:02 ` sources Christopher Faylor
1999-02-28 23:02 ` sources Don Sharp
-- strict thread matches above, loose matches on Subject: below --
2003-03-20 14:53 Sources Nicholas Marsh
2003-03-20 16:16 ` Sources Pavel Tsekov
[not found] <000f01be5909$92381800$29acdfd0@InspirePharm.Com>
1999-02-15 11:14 ` sources Don Sharp
1999-02-28 23:02 ` sources Don Sharp
1999-02-15 9:49 sources Earnie Boyd
1999-02-15 11:16 ` sources Don Sharp
1999-02-28 23:02 ` sources Don Sharp
1999-02-28 23:02 ` sources Earnie Boyd
1999-02-15 9:20 sources Don Sharp
[not found] ` < 36C856B3.E5010221@dddandr.octacon.co.uk >
1999-02-15 20:14 ` sources Christopher Faylor
[not found] ` < 19990215231439.B11574@cygnus.com >
1999-02-15 21:03 ` sources Pierre A. Humblet
[not found] ` < 3.0.5.32.19990216000426.00825350@pop.ne.mediaone.net >
1999-02-15 21:26 ` sources Christopher Faylor
1999-02-28 23:02 ` sources Christopher Faylor
1999-02-28 23:02 ` sources Pierre A. Humblet
1999-02-16 9:04 ` sources Henry J. Cobb
[not found] ` < 199902160908.5731104.6@www.web-alive.com >
1999-02-16 16:11 ` sources Christopher Faylor
1999-02-28 23:02 ` sources Christopher Faylor
1999-02-28 23:02 ` sources Henry J. Cobb
1999-02-28 23:02 ` sources Christopher Faylor
1999-02-28 23:02 ` sources Don Sharp
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=19990216202649.B16511@cygnus.com \
--to=cgf@cygnus.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=dwsharp@iee.org \
/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).