Talk:Yacc: Difference between revisions
Hm nevermind, confused yacc with lex |
→Most C parsing is no longer Yacc-based: new section |
||
Line 18: | Line 18: | ||
There's a (growing) list of languages in which yacc is claimed to have been reimplemented. Some are reasonably notable, and can probably be reliably sourced. But the list presently is unsourced. [[User:Tedickey|Tedickey]] ([[User talk:Tedickey|talk]]) 13:24, 29 March 2009 (UTC) |
There's a (growing) list of languages in which yacc is claimed to have been reimplemented. Some are reasonably notable, and can probably be reliably sourced. But the list presently is unsourced. [[User:Tedickey|Tedickey]] ([[User talk:Tedickey|talk]]) 13:24, 29 March 2009 (UTC) |
||
== Most C parsing is no longer Yacc-based == |
|||
I corrected the original flat statement that C parsers are Yacc-based. There may still be some out there, but as of 28 Feb 2006, the all-important GCC frontend is not generated by Yacc or any tool derived from Yacc -- it's a hand-written recursive descent parser. |
|||
I also added a citation needed. We need a reference to show that the original AT&T/K&R C compilers were Yacc-based. (Was the first UNIX C compiler YACC based? I think so, but I'm not sure.) To see that as of 4.1, GCC is not YACC-based, [http://gcc.gnu.org/gcc-4.1/changes.html there is this reference] -- it's long but searchable. Look for this statement: "The old Bison-based C and Objective-C parser has been replaced by a new, faster hand-written recursive-descent parser." |
Revision as of 00:26, 14 September 2010
What kind of imnage are we looking for? Yacc input? The output? It's a program, what do I tak a picture of? RJFJR 02:44, Jun 17, 2005 (UTC)
Agree. Is a program, no sense to have an image.
Should we site some sources for all the languages it's been ported to? I've neer heard of a Limbo or Ratfor Yacc.
When did the original yacc came out? I think this is something missing in the article. Frigoris (talk) 01:29, 31 October 2008 (UTC)
- It references the paper by Johnson in 1979 (perhaps older than that, but one cannot tell from the paper itself). Tedickey (talk) 01:59, 31 October 2008 (UTC)
Lowercase for yacc?
Though the title of this article is in lowercase by {{Lowercase}}, I can find that uppercase is used in quite a number of places in the article. Should they be changed to lowercase? --Quest for Truth (talk) 11:13, 30 January 2009 (UTC)
- probably (though as a stylistic issue, I'd leave a leading cap on sentences) Tedickey (talk) 14:16, 30 January 2009 (UTC)
Implementations in various languages
There's a (growing) list of languages in which yacc is claimed to have been reimplemented. Some are reasonably notable, and can probably be reliably sourced. But the list presently is unsourced. Tedickey (talk) 13:24, 29 March 2009 (UTC)
Most C parsing is no longer Yacc-based
I corrected the original flat statement that C parsers are Yacc-based. There may still be some out there, but as of 28 Feb 2006, the all-important GCC frontend is not generated by Yacc or any tool derived from Yacc -- it's a hand-written recursive descent parser.
I also added a citation needed. We need a reference to show that the original AT&T/K&R C compilers were Yacc-based. (Was the first UNIX C compiler YACC based? I think so, but I'm not sure.) To see that as of 4.1, GCC is not YACC-based, there is this reference -- it's long but searchable. Look for this statement: "The old Bison-based C and Objective-C parser has been replaced by a new, faster hand-written recursive-descent parser."