Bison中解释器的if/while/for语句实现问题求助

It looks like your Bison grammar correctly defines the syntax for if/elif/else statements, but you're missing the semantic logic that ties the condition result to whether the statement block executes. Right now, your parser just recognizes the syntax, but doesn't actually check the rule's value to decide whether to run the smt block. Let's break down the problem and fix it.

The Root Issue #

Your rule rule calculates a boolean result (1 for true, 0 for false) and stores it in $<int_val>$, but none of your if_block or elif_block rules use this value to control execution. Bison only handles syntax validation by default—you have to add semantic actions to tell your interpreter "run this block only if the condition is true".

Step-by-Step Fix #

First, make sure you've defined your union types correctly (to pass values between rules):

%union {
    int int_val;          // For boolean condition results
    data_type data_val;   // For your expression values (adjust to your actual type)
    stmt_type* stmt_node; // Optional: If building an AST, use this for statement nodes
}

// Declare types for non-terminals
%type <int_val> rule
%type <stmt_node> smt if_block elif_block

Then, update your rules with semantic actions that respect the condition result:

1. Basic If Block

if_block: IF '(' rule ')' '{' smt '}' 
    {
        // Execute the statement block ONLY if the condition is true (1)
        if ($3 == 1) {
            execute_statement($6); // Replace with your statement execution function
        }
        // If building an AST, create an IfNode instead:
        // $$ = create_if_node($3, $6, NULL);
    }

2. If-Else Block

| IF '(' rule ')' '{' smt '}' ELSE '{' smt '}'
    {
        if ($3 == 1) {
            execute_statement($6);
        } else {
            execute_statement($10);
        }
        // AST alternative:
        // $$ = create_if_node($3, $6, $10);
    }

3. If-Elif-Else Block

For chained elifs, we need to handle sequential condition checks:

| IF '(' rule ')' '{' smt '}' elif_block ELSE '{' smt '}'
    {
        if ($3 == 1) {
            execute_statement($6);
        } else {
            // Pass the else block to the elif chain (run if no elifs match)
            execute_elif_block($8, $10);
        }
    }

4. Elif Block Handling

elif_block: ELIF '(' rule ')' '{' smt '}'
    {
        if ($3 == 1) {
            execute_statement($6);
            // If using AST, mark this as matched to skip later elifs/else
            $$ = create_elif_node($3, $6, NULL);
        }
    }
| ELIF '(' rule ')' '{' smt '}' elif_block
    {
        if ($3 == 1) {
            execute_statement($6);
        } else {
            execute_elif_block($8, NULL);
        }
        // AST alternative:
        // $$ = create_elif_node($3, $6, $8);
    }

Critical Checks #

• Verify your check function: Make sure it returns 1 when the condition is true (e.g., equality holds) and 0 when false. If this is reversed, your logic will run the wrong blocks. Add debug prints to confirm:

  rule: exp EQUAL_T exp 
      {
          $<int_val>$ = check($<data_val>1, $<data_val>3);
          printf("Condition result: %d\n", $<int_val>$); // Debug check
      }
  

• If you're building an AST instead of executing immediately: Focus on creating nested condition nodes, then handle the conditional execution when traversing the AST later (not during parsing).

Key Takeaway #

Bison's job is to parse syntax into a structure you can work with—you have to explicitly define what that structure does. Without tying the condition's boolean result to statement execution, your interpreter will run every block regardless of the condition.

内容的提问来源于stack exchange，提问作者AshkanAbd