Re: [2/5] dtc: Use flex's YY_USER_ACTION feature to avoid code duplication
From: Jon Loeliger <hidden>
Date: 2008-10-02 16:25:27
Possibly related (same subject, not in this thread)
- 2008-10-04 · Re: [2/5] dtc: Use flex's YY_USER_ACTION feature to avoid code duplication · David Gibson <hidden>
- 2008-10-03 · Re: [2/5] dtc: Use flex's YY_USER_ACTION feature to avoid code duplication · Jon Loeliger <hidden>
- 2008-10-03 · Re: [2/5] dtc: Use flex's YY_USER_ACTION feature to avoid code duplication · Jon Loeliger <hidden>
- 2008-10-02 · [2/5] dtc: Use flex's YY_USER_ACTION feature to avoid code duplication · David Gibson <hidden>
On Fri, 2008-10-03 at 00:05 +1000, David Gibson wrote:
Current, every lexer rule starts with some boiler plate to update the yylloc value for use by the parser. One of the rules, even mistakenly has a redundant allocation to one of the members. This patch uses the flex YY_USER_ACTION macro hook, which is executed before every rule to avoid this duplication. Signed-off-by: David Gibson <redacted> ---
This, and the xstrdup() change are both excellent suggestions. jdl