From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Phil Pennock <phil@athenaeum.demon.co.uk>, zsh-workers@math.gatech.edu
Subject: Re: Arithmetic expression (bug?)
Date: Sun, 15 Nov 1998 14:21:06 -0800 [thread overview]
Message-ID: <981115142107.ZM29503@candle.brasslantern.com> (raw)
In-Reply-To: <199811050140.BAA02822@athenaeum.demon.co.uk>
Catching up on some more old stuff:
On Nov 5, 1:40am, Phil Pennock wrote:
} Subject: Re: Arithmetic expression (bug?)
}
} Typing away merrily, Bernd Eggink produced the immortal words:
} > > -----------------------------< cut here >-------------------------------
} > > foo=alpha
} > > print -- ${(l<$[10]><x>)foo}
} > > print -- ${(l<10><x>)foo}
} > > -----------------------------< cut here >-------------------------------
} > > why does the third line produce:
} > > ./testfile: error in flags [3]
} > > ?
} >
} > I can't reproduce this.
I *can* reproduce this. I can reproduce it in 3.0.5, too.
The problem is with the parse:
l<$[10]><x> parses as
'l' '<' String Inbrack '1' '0' Outbrack '>' '<' 'x' '>'
l<10><x> parses as
'l' Inang '1' '0' Outang '<' 'x' '>'
Now because (Inang != '<') the error is reported when looking at the <x>
after correctly scanning the <10>.
I'm not fluent enough with the parser to understand why that happens, or
whether the fix is to treat Inang, Inpar, etc. as equal to '<', '(', etc.
in the substitution code, or to actually modify the parser.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1998-11-15 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-04 21:34 Phil Pennock
1998-11-04 22:05 ` Bernd Eggink
1998-11-05 1:40 ` Phil Pennock
1998-11-15 22:21 ` Bart Schaefer [this message]
1998-11-15 22:46 ` Bart Schaefer
1998-11-15 23:19 ` PATCH: 3.1.5 and 3.0.5: ${(l<e><s1><s2>)param} (was Re: Arithmetic expression (bug?)) Bart Schaefer
1998-11-15 23:25 ` More about ${(l:e::s1::s2:)param} Bart Schaefer
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=981115142107.ZM29503@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=phil@athenaeum.demon.co.uk \
--cc=zsh-workers@math.gatech.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).