|coding conventions email@example.com (2003-02-05)|
|Re: coding conventions firstname.lastname@example.org (2003-02-11)|
|Re: coding conventions email@example.com (2003-02-21)|
|Re: coding conventions firstname.lastname@example.org (2003-02-24)|
|From:||email@example.com (Alex Colvin)|
|Date:||11 Feb 2003 02:14:05 -0500|
|Organization:||The World Public Access UNIX, Brookline, MA|
|Posted-Date:||11 Feb 2003 02:14:05 EST|
>I'm fairly new to this flex/bison stuff, and I was wondering - is
>there a recommended coding convention for flex/bison ? like for
>example should I have named the "subpart" differently, etc.
> L200_GLOBAL procedure_decl_subpart
> | L200_EXTERNAL procedure_decl_subpart
> L200_PROCEDURE L200_IDENTIFIER L200_SEMICOLON
I don't have any formal style guide, but I'll push the convention that the
yacc actions should be kept as short as possible, either an assignment or
a function call. Not only does long precedural code make the grammar hard
to follow, but you don't want to put anything you might need to debug in
your *.y file.
What's with the L200_...?
mac the naïf
Return to the
Search the comp.compilers archives again.