|Anonymous | Login||2021-11-29 11:12 UTC|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details|
|ID||Category||Severity||Type||Date Submitted||Last Update|
|0000517||[1003.1(2008)/Issue 7] Shell and Utilities||Objection||Enhancement Request||2011-11-25 17:08||2012-08-29 16:27|
|Section||(section number or name, can be interface name)|
|Page Number||(page or range of pages)|
|Line Number||(Line or range of lines)|
|Final Accepted Text|
|Summary||0000517: EBNF support|
It would be nice if yacc supported EBNF rather than BNF, as
1. It makes it much easier to express certain things.
2. EBNF is backwards compatible with BNF.
|Desired Action||EBNF has been standardized as ISO/IEC 14977:1999(E). POSIX could merely link to that document.|
|Tags||No tags attached.|
Could you please list the new features you have in mind?
The current UNIX yacc implementation can be found e.g. at:
and it seems to make sense to understand how much code needs to be changed.
The official standard documents both the differences between BNF and EBNF and has a list of advantages that EBNF brings. I forgot to mention this, but it can be downloaded for free from ISO's website: http://standards.iso.org/ittf/PubliclyAvailableStandards/s026153_ISO_IEC_14977_1996(E).zip [^]
Note that since EBNF cannot express anything that BNF can't, the code that generates the parser shouldn't really require any changes (mine didn't).
|2011-11-25 17:08||Love4Boobies||New Issue|
|2011-11-25 17:08||Love4Boobies||Name||=> Bogdan Barbu|
|2011-11-25 17:08||Love4Boobies||URL||=> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/yacc.html [^]|
|2011-11-25 17:08||Love4Boobies||Section||=> (section number or name, can be interface name)|
|2011-11-28 15:26||joerg||Note Added: 0001059|
|2011-11-28 16:52||Love4Boobies||Note Added: 0001062|
|2012-08-29 16:27||msbrown||Project||Online Pubs => 1003.1(2008)/Issue 7|
|Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group|