Chris,
The project is for a CS class. I don't know if I can submit it to the
list. I don't want my code out on the internet. I don't know how my prof
would feel about that. That being said, I discovered that if I add any code
Bison's parse goes wrong. Even if I add an empty action the parse goes
wrong.
For example:
expr : expr addop expr { }
causes Bison to parse a = b + c + d
c + d = something
b + something = something
On the note of sending data up the stack, my prof sent me an email with a
example script that I am going to try tonight. Why do you think adding an
action to the rule causes Bison to to parse incorrectly?
Thanks again for all the help.
On Tue, Aug 10, 2010 at 1:42 PM, Chris verBurg <cheetomons...@gmail.com>wrote:
>
> (Replying individually for a quick question)
>
> I just got back into town and am catching up on email -- have you posted or
> otherwise sent out your actual bison source file? Would that be possible to
> do? It might not be, due to company IP concerns, etc, but at least those of
> us trying to help you wouldn't be shooting in the dark so much. :)
>
> -Chris
>
>
>
> On Mon, Aug 9, 2010 at 2:27 PM, Sasan Forghani <sasanforgh...@gmail.com>wrote:
>
>> After the %left issue, the issue left is how to send data up the stack.
>> Once a production such as expr : expr + expr is reduced and the actions
>> performed how can I send data to the next reduction?
>> _______________________________________________
>> help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
>>
>
>
_______________________________________________
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
