[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: push parser implemenation
From: |
Joel E. Denny |
Subject: |
Re: push parser implemenation |
Date: |
Wed, 19 Apr 2006 21:26:50 -0400 (EDT) |
On Mon, 17 Apr 2006, Bob Rossi wrote:
> Hi everyone, I hope I can get some suggestions soon. I don't want this
> to be forgotten about.
>
> Either we can make the push parser a separate file
There are 4 skeletons now. Push parser mode could be desirable for any of
them. Coding the push parser in separate skeletons could mean a total of
8 skeletons and a lot of redundant code. This doesn't seem like the right
way to go.
>, we can allow the user to loose the 10% speed performance
I'm not concerned with this performance loss much for my current usage,
but I imagine this is not acceptable to many Bison users.
>, I can attempt to do the above
> suggestion, or
>
> I can see what happens if I declare the struct globally, and when in
> push-yacc and pure-yacc mode, declare variables on the stack with the
> same name as the struct's fields. This may improve the speed.
I don't have time to study these two alternatives and form a thoughtful
opinion. It seems that others don't at the moment either. Maybe you
could try one or both and report your findings.
Joel
Re: push parser implemenation, Bob Rossi, 2006/04/07
Re: push parser implemenation, Bob Rossi, 2006/04/07
Re: push parser implemenation, Bob Rossi, 2006/04/08
Re: push parser implemenation, Akim Demaille, 2006/04/20
Re: push parser implemenation, Akim Demaille, 2006/04/20
Re: push parser implemenation, Bob Rossi, 2006/04/20
Re: push parser implemenation, Akim Demaille, 2006/04/24
Re: push parser implemenation, Joel E. Denny, 2006/04/24
Re: push parser implemenation, Akim Demaille, 2006/04/25
Re: push parser implemenation, Bob Rossi, 2006/04/26
Re: push parser implemenation, Akim Demaille, 2006/04/27