summaryrefslogtreecommitdiff
path: root/src/interfaces/ecpg/preproc/README.parser
diff options
context:
space:
mode:
authorMichael Meskes <meskes@postgresql.org>2011-03-03 13:43:50 +0100
committerMichael Meskes <meskes@postgresql.org>2011-03-03 13:43:50 +0100
commit32fce70564999a90d48a27c4279a8908e90f3ece (patch)
tree410b29b53ea44b559679998fba5789d22289c2af /src/interfaces/ecpg/preproc/README.parser
parent8e2d8b1497ac64142bb7df05e39a58ebf3e62bf6 (diff)
Added new version of ecpg's parser generator script. This one was written by
Andy Colson <andy@squeakycode.net>.
Diffstat (limited to 'src/interfaces/ecpg/preproc/README.parser')
-rw-r--r--src/interfaces/ecpg/preproc/README.parser4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/interfaces/ecpg/preproc/README.parser b/src/interfaces/ecpg/preproc/README.parser
index ddc3061d486..6d6daac4ba3 100644
--- a/src/interfaces/ecpg/preproc/README.parser
+++ b/src/interfaces/ecpg/preproc/README.parser
@@ -3,7 +3,7 @@ ECPG modifies and extends the core grammar in a way that
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 by parse.pl.
+ passed to the server, this is done by parse2.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,
@@ -20,7 +20,7 @@ rules concatenated together. e.g. if gram.y has this:
ruleA: tokenA tokenB tokenC {...}
then "dumpedtokens" is "ruleAtokenAtokenBtokenC".
"postfix" above can be:
-a) "block" - the automatic rule created by parse.pl is completely
+a) "block" - the automatic rule created by parse2.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