Tracking bound syntax pattern variables with syntax-parse

Go to file

Georges Dupéron 25ed9ec068 Integrate auto-syntax-e, as this needs a deep modification in the syntax-mapping struct		2017-02-01 08:01:18 +01:00
case	Integrate auto-syntax-e, as this needs a deep modification in the syntax-mapping struct	2017-02-01 08:01:18 +01:00
parse	Integrate auto-syntax-e, as this needs a deep modification in the syntax-mapping struct	2017-02-01 08:01:18 +01:00
scribblings	Fixed define-pvars (was not defining the unique-at-runtime variables)	2017-01-28 05:17:32 +01:00
test	Improved coverage	2017-01-28 05:17:00 +01:00
.gitignore	Added package files	2017-01-28 05:16:16 +01:00
.travis.yml	Run tests properly (without -x), and avoid OOM on Travis.	2017-01-28 05:17:00 +01:00
case.rkt	Modified syntax-case & friends to use with-pvars. Closes 181 current-pvars: use in syntax-case, with-syntax, define/with-syntax, is there any with-parse?	2017-01-28 05:16:48 +01:00
current-pvars.rkt	Fixed define-pvars (was not defining the unique-at-runtime variables)	2017-01-28 05:17:32 +01:00
info.rkt	Integrate auto-syntax-e, as this needs a deep modification in the syntax-mapping struct	2017-02-01 08:01:18 +01:00
LICENSE	Imported files from `28f1df4cff`	2017-01-28 05:16:11 +01:00
LICENSE.txt	Added package files	2017-01-28 05:16:16 +01:00
main.rkt	Fixed docs for (define-pvars (pvar ...)), should be (define-pvars pvar ...)	2017-01-28 05:16:54 +01:00
parse.rkt	Failed attempt at making metafunctions from syntax/parse/experimental/template and stxparse-info/parse/experimental/template compatible. I can manage to extract the binding from syntax/parse/…, but it seems to recognize a different struct (e.g. as if they were struct instances from two different phases)	2017-01-28 05:16:50 +01:00
README.md	Improved coverage	2017-01-28 05:17:00 +01:00

README.md

stxparse-info

The module stxparse-info/parse is a patched version of syntax/parse which tracks which syntax pattern variables are bound. This allows some libraries to change the way syntax pattern variables work.

For example, phc-graph/subtemplate automatically derives temporary identifiers when a template contains yᵢ …, and xᵢ is a pattern variable. To know from which varᵢ the yᵢ … identifiers must be derived, phc-graph/subtemplate needs to know which syntax pattern variables are within scope.

To use this package, simply require stxparse-info/pares instead of syntax/parse Additionally, it is possible to use the for-syntax function (current-pvars) from stxparse-info/current-pvars to access the list of currently-bound pattern variables, and the macro (with-pvars (pvar ...) . body) can be used to add new pattern variables to the list.