Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <20160411133145.486788a5@pwslap01u.europe.root.pri>
References: <CAHYJk3TY5kU0fXDkk2iO7kRJhhMTS1f4a9Am1ueN4wCXOQ7Hsg@mail.gmail.com>
	<160410151105.ZM21544@torch.brasslantern.com>
	<20160411093738.11406966@pwslap01u.europe.root.pri>
	<CAHYJk3SEeghkbpLCE26bG_76nM5PYp9MF68AO1ue00DHTwRV6A@mail.gmail.com>
	<20160411112941.579d8157@pwslap01u.europe.root.pri>
	<CAHYJk3QkC_jDq94ax2vMZUCaU2iELFO7kk49ogQUg-qafDtgPA@mail.gmail.com>
	<20160411120716.06a6d1c9@pwslap01u.europe.root.pri>
	<CAHYJk3Qc8WsRAxav6wT8MmoEKj-hDByAA3ZCWHHbTt=+CaUQxQ@mail.gmail.com>
	<20160411133145.486788a5@pwslap01u.europe.root.pri>
Date: Mon, 11 Apr 2016 15:45:02 +0200
Message-ID: <CAHYJk3TKQx4pB7uKjxwVdU+QQyeJTxo7qj6w0Xibq2V7J_Qsqw@mail.gmail.com>
Subject: Re: Allow slash in alternation patterns in limited cases?
From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh workers <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 11, 2016 at 2:31 PM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
> On Mon, 11 Apr 2016 14:06:10 +0200
> Mikael Magnusson <mikachu@gmail.com> wrote:
>
>> On Mon, Apr 11, 2016 at 1:07 PM, Peter Stephenson
>> <p.stephenson@samsung.com> wrote:
>> > The point is that, unlike the ~ case which is just a flag passed in to
>> > the pattern match parser, it would longer done by pattern matching at
>> > all.  It would be done in the glob code.  The pattern match code would
>> > see the foo, bar, baz, bong, and it would it be reassembled higher up.
>> > So it's not so much incompatible as something utterly different.
>>
>> This is already the same difference we have between (foo|bar) in
>> globbing and pattern matching though. If it's a glob, it's handled
>> recursively by scanner() and if it's pattern, it's somewhere else (I
>> don't even know where the general pattern matching code is by heart).
>
> No, expressions like (foo|bar) are *only* handled by the pattern
> matcher.  The scanner's sole responsibility is to tell the pattern
> matcher whether or not it should stop if it sees a "/".

Ah, that explains it :). Thanks.

-- 
Mikael Magnusson