Closed sangisos closed 8 years ago
Request for comment @mewmew
An initial implementation of isAssignment
was added in commit 4120fc5af3879a2cb3982ef67f83c0152033e2cc.
Would be happy to discuss this issue in greater detail next time we meet, as it is a non-trivial one.
Ok, lets have a meeting tomorrow about these decisions.
Ok, lets have a meeting tomorrow about these decisions.
Wonderful. Meet up at around 14dk?
Sure, sounds good.
Med Vänliga Hälsningar Alexander Andersson On 29 Apr 2016 02:09, "Robin Eklind" notifications@github.com wrote:
Ok, lets have a meeting tomorrow about these decisions.
Wonderful. Meet up at around 14dk?
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/mewmew/uc/issues/55#issuecomment-215598536
Closing for now. Re-opened in the future to discuss specific issues with the current implementation, or to further validate the implementation against the C specification.
from test file incorrect/semantic/se25.c:
Check assignments for lvalue equivalent type, preferably in a future proof manner. In the future, support for array names and dereferenced pointer expressions to be assigned to will be added.
This should perhaps be done before before type checking, as the error messages will make more sense for files like incorrect/semantic/se11.c:
now giving error message:
invalid operation: a = 1 (type mismatch between "int(void)" and "int")