https://d.puremagic.com/issues/show_bug.cgi?id=12306


Vladimir Panteleev <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]


--- Comment #2 from Vladimir Panteleev <[email protected]> 2014-03-07 
01:28:20 EET ---
Looks like the compiler parses the array declaration as an associative array
(and conservatively assumes that "point.x" is a type), then when it realizes it
is in fact a static array, it does not reparse the whole "point.x" expression
correctly (it just looks at the last symbol, x). Making it clear that it is an
expression, e.g. adding "+0", also fixes compilation.

Fixing this is not trivial as the expression that the compiler sees in the
array index is not saved. I think the correct fix would be to switch the
parsing order: Assume that the array "index" is an expression, then, if it
resolves to a type, reinterpret the whole thing as an associative array.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

Reply via email to