After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 110809 - parse grammer has conflicts
parse grammer has conflicts
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other other
: Normal normal
: 0.6.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-04-15 04:23 UTC by Joshua N Pritikin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Joshua N Pritikin 2003-04-15 04:23:41 UTC 
./grammar.y: conflicts: 32 shift/reduce, 6 reduce/reduce

This may not be a bug, but so much ambiguity can make the parser slow and
certainly hard to maintain.

i recommend PCCTS.  It's much better at handling ambiguity than bison/flex.
 So if you are going to rewrite the parser, use something like PCCTS.
Comment 1 Benjamin Otte (Company) 2003-04-15 09:59:31 UTC 
Most parse grammars will have conflicts, so this behaviour must not be
a bug.

reduce/reduce conflicts should eventually be removed, but until the
parser is not complete, I'm not going to optimize the grammar.
shift/reduce conflicts are expected, there is even a way to suppress
this warning (which i'm not using because of the frequent updates atm).

But since the behaviour is well defined for both cases there should
not be any errors.
Comment 2 Joshua N Pritikin 2003-04-26 11:51:43 UTC 
Bah!  i guess this isn't important enough to keep an open bug.