Fixed bugs in stack.c #61
Conversation
Removed the else-block of "if (c == '-')" and restructured the clear command so the "stack is empty" message is not displayed an extra time after the c command has already been called. E.g if on the first line you type 'c', the message is displayed. On the next line, the message is displayed again even if you only typed "9 9+" because the previous code structure in the clear function forced the sp variable to go down to -1.
chapter_4/exercise_4_04/stack.c
Outdated
| /* do | ||
| { | ||
| stack[sp] = 0.0; | ||
| } while (sp--); | ||
| */ | ||
| // Replacing the above commented code with this one ensures messages of "stack empty" aren't displayed an extra time after c command is called in the program |
There was a problem hiding this comment.
@sadeem-albir Remove the commented code before merging.
There was a problem hiding this comment.
Commented code has been removed.
modified the clear function
Removed else-block in if (c == '-')
| while (sp > 0) | ||
| { | ||
| stack[sp] = 0.0; | ||
| } while (sp--); | ||
| stack[--sp] = 0.0; | ||
| } |
There was a problem hiding this comment.
@sadeem-albir Is this code required to change? What's the bug here? Is it that pre decrement that useful?
There was a problem hiding this comment.
@ohkimur If my assumption is correct, the sp works the same as buf and bufp. whenever you add something to the stack, you do stack[sp++], meaning the current index (zero) will be assigned then sp will be the next unassigned index. So by using that other while-loop instead, you ensure you move to the previous assigned sp until you reach zero. Also, in the do-loop, even if sp was zero, it will be decremented, undesirably becoming -1.
There was a problem hiding this comment.
@sadeem-albir With this approach, I think the first location from sp will be always empty. Can you verify that? What do you think would be better here? If the previous approach is better, I propose we go with that.
There was a problem hiding this comment.
@ohkimur Not necessarily a negative impact. As you see in the pop function, you return stack[--sp] so sp is meant to be empty at whatever current index it is lying at for the moment, and when we need to use a value from the stack, we simply call the previous index of sp, so if the stack was [1, 2, 3, 0] and sp is 3, calling pop will return the value of 3 at index 2. The change I have proposed ensures consistency with the way sp changes in the other stack functions, but if you believe staying at the previous change is better for the program, then the change doesn't have to be merged.
Removed the else-block of "if (c == '-')" and restructured the clear command so the "stack is empty" message is not displayed an extra time after the c command has already been called. E.g if on the first line you type 'c', the message is displayed. On the next line, the message is displayed again even if you only typed "9 9+" because the previous code structure in the clear function forced the sp variable to go down to -1.