Possible parsing bug with alternate for-loop syntax

Possible parsing bug with alternate for-loop syntax

[Mikael Magnusson]

17:44:25 <Mikachu> > for a (1) {echo hi}
17:44:26 <machabot> Mikachu: hi
17:44:29 <Mikachu> > for a (1) {a=hi}; echo $a
17:44:38 <machabot> Mikachu: Timeout (no output).
17:44:36 <Mikachu> > for a (1) {a=hi} }; echo $a
17:44:39 <machabot> Mikachu: hi}
17:45:17 <Mikachu> > for a (1) {builtin local a=hi}; echo $a
17:45:18 <machabot> Mikachu: hi
17:45:22 <Mikachu> > for a (1) {local a=hi}; echo $a
17:45:30 <machabot> Mikachu: Timeout (no output).
17:45:26 <Mikachu> nice
17:45:37 <Mikachu> you get the bug for reserved word local but not for
builtin local

The documentation does state the syntax is { list } with the space
included, but this still seemed somewhat surprising to me.

-- 
Mikael Magnusson

Re: Possible parsing bug with alternate for-loop syntax

[Bart Schaefer]

Doesn't have anything to do with for-loop syntax:

torch% a=hi}; echo $a
hi}
torch% {a=hi}; echo $a
cursh> 

It's assignment parsing.  The "}" is always considered part of the
value assigned to the variable.

Re: Possible parsing bug with alternate for-loop syntax

[Mikael Magnusson]

On Sat, Jun 11, 2016 at 8:31 PM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> Doesn't have anything to do with for-loop syntax:
>
> torch% a=hi}; echo $a
> hi}
> torch% {a=hi}; echo $a
> cursh>
>
> It's assignment parsing.  The "}" is always considered part of the
> value assigned to the variable.

Ah, you're right, the same thing happens with function parsing as well,
% () {a=hi}
function>

-- 
Mikael Magnusson