[Pnet-developers] [bug #7485] Non-initialized variable in for-loop shall not be compiled by cscc

[Deryk Robosson]

Follow-up Comment #2, bug #7485 (project dotgnu-pnet):

Digging a bit further, this doesn't appear to be tied directly to the FOR
keyword and related parsing.  It can occur elsewhere as well as demonstrated
in the attached test case.

ExpressionStatementList->ExpressionStatement->InnerExpressionStatement->AssignmentExpression
would be the flow I would expect to happen in this circumstance for the CS
case.  The first entry for AssignmentExpression is '=' though I can only
assume what $1 and $3 should be (variable and value?) as passed to
MakeBinary.  Klaus suggested during the course of conversation, "the first
case in AssignmentExpression should set a kind of flag on the variable that
it is initialized".

Rhys, can you offer any ideas or suggestions on this?
    _______________________________________________________

Additional Item Attachment:

File name: testcase.c                     Size:0 KB
Additional C test case
<http://savannah.gnu.org/bugs/download.php?item_id=7485&item_file_id=2574>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=7485>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/