@$(missing) flex $< $@

preproc.y: ../../../backend/parser/gram.yparse2.pl ecpg.addons ecpg.header ecpg.tokens ecpg.trailer ecpg.type

$(PERL)$(srcdir)/parse2.pl$(srcdir)<$<>$@

preproc.y: ../../../backend/parser/gram.yparse.pl ecpg.addons ecpg.header ecpg.tokens ecpg.trailer ecpg.type

$(PERL)$(srcdir)/parse.pl$(srcdir)<$<>$@

$(PERL)$(srcdir)/check_rules.pl$(srcdir)$<

ecpg_keywords.oc_keywords.okeywords.opreproc.oparser.o: preproc.h

defined in ecpg.tokens, types are defined in ecpg.type

2) most tokens from the core grammar are simply converted

to literals concatenated together to form the SQL string

passed to the server, this is done byparse2.pl.

passed to the server, this is done byparse.pl.

3) some rules need side-effects, actions are either added

or completely overridden (compared to the basic token

concatenation) for them, these are defined in ecpg.addons,

ruleA: tokenA tokenB tokenC {...}

then "dumpedtokens" is "ruleAtokenAtokenBtokenC".

"postfix" above can be:

a) "block" - the automatic rule created byparse2.pl is completely

a) "block" - the automatic rule created byparse.pl is completely

overridden, the code block has to be written completely as

it were in a plain bison grammar

b) "rule" - the automatic rule is extended on, so new syntaxes

* CONNECTION can be added back in all_unreserved_keyword, but CURRENT and

* INPUT are reserved for ecpg purposes.

*

* The mentioned exclusions are done by $replace_line settings inparse2.pl.

* The mentioned exclusions are done by $replace_line settings inparse.pl.

*/

all_unreserved_keyword: unreserved_keyword{ $$ = $1; }

| ECPGunreserved_interval{ $$ = $1; }