|--- |FIXED
--- Comment #14 from Dlang Bot ---
dlang/dmd pull request #15410 "Fix Issue 7184 - parse error on *(x)++" was
merged into master:
- 50e5492929f4afe27177824371407094d93029dc by Nick Treleaven:
Fix Issue 7184 - parse error on *(x)++
https://github.com/dlang/dmd/pull/15410
--
created dlang/dmd pull request #15410 "Fix Issue 7184 - parse error on
*(x)++" fixing this issue:
- Fix Issue 7184 - parse error on *(x)++
https://github.com/dlang/dmd/pull/15410
--
https://issues.dlang.org/show_bug.cgi?id=7184
Iain Buclaw changed:
What|Removed |Added
Priority|P2 |P3
--
https://issues.dlang.org/show_bug.cgi?id=7184
RazvanN changed:
What|Removed |Added
CC||bukni...@yandex.ru
--- Comment #12 from RazvanN
https://issues.dlang.org/show_bug.cgi?id=7184
Seb changed:
What|Removed |Added
CC||greensunn...@gmail.com
---
https://issues.dlang.org/show_bug.cgi?id=7184
--- Comment #10 from RazvanN ---
(In reply to timon.gehr from comment #9)
> (In reply to timon.gehr from comment #8)
> > (In reply to RazvanN from comment #1)
> > > Issuing an error is the correct behavior. As you can see
https://issues.dlang.org/show_bug.cgi?id=7184
--- Comment #9 from timon.g...@gmx.ch ---
(In reply to timon.gehr from comment #8)
> (In reply to RazvanN from comment #1)
> > Issuing an error is the correct behavior. As you can see in the grammar
> > [1],
> > *(x)++ is parsed the following way:
https://issues.dlang.org/show_bug.cgi?id=7184
--- Comment #8 from timon.g...@gmx.ch ---
(In reply to RazvanN from comment #1)
> Issuing an error is the correct behavior. As you can see in the grammar [1],
> *(x)++ is parsed the following way: *UnaryExpression. If a parenthesis is
> encountered,
https://issues.dlang.org/show_bug.cgi?id=7184
--- Comment #7 from Simen Kjaeraas ---
Unsurprisingly, the function call variant is somewhat unfixable. (T)(a+b) is a
very common cast in C, and looks a lot like a function call where T is a
function. Even (T)(1,2,3) is valid
https://issues.dlang.org/show_bug.cgi?id=7184
--- Comment #6 from Simen Kjaeraas ---
You're at least partly right, though (a[b]).c does work. The smallest example
of this bug is probably this:
unittest {
(a)++;
}
That should of course fail to compile as well, but
https://issues.dlang.org/show_bug.cgi?id=7184
--- Comment #5 from anonymous4 ---
Ah, so the problem is that in expression (a[b]).c it's undecidable if the
braced expression should be parsed as type or value.
--
https://issues.dlang.org/show_bug.cgi?id=7184
--- Comment #4 from RazvanN ---
(In reply to Simen Kjaeraas from comment #3)
> (In reply to RazvanN from comment #1)
> > The behavior is according to the spec, so I will close this as invalid.
>
> It's perfectly possible
https://issues.dlang.org/show_bug.cgi?id=7184
Simen Kjaeraas changed:
What|Removed |Added
Keywords||spec
https://issues.dlang.org/show_bug.cgi?id=7184
--- Comment #2 from anonymous4 ---
Is the grammar ordered? It expects braces through PowExpression:
https://dlang.org/spec/grammar.html#PowExpression
--
https://issues.dlang.org/show_bug.cgi?id=7184
RazvanN changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.dlang.org/show_bug.cgi?id=7184
Andrei Alexandrescu changed:
What|Removed |Added
Keywords||bootcamp
16 matches
Mail list logo