Tracking bound syntax pattern variables with syntax-parse
Go to file
2017-01-28 05:17:00 +01:00
case Bugfix and tests for define/with-syntax 2017-01-28 05:16:58 +01:00
parse Removed parse/private/keywords.rkt, to improve compatibility with the official syntax/parse (that file defines ~optional etc.) 2017-01-28 05:16:59 +01:00
scribblings Support #:properties on all four of (quasi)template(/loc), instead of just template. 2017-01-28 05:16:57 +01:00
test Bugfix and tests for define/with-syntax 2017-01-28 05:16:58 +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 Support #:properties on all four of (quasi)template(/loc), instead of just template. 2017-01-28 05:16:57 +01:00
info.rkt Removed parse/private/keywords.rkt, to improve compatibility with the official syntax/parse (that file defines ~optional etc.) 2017-01-28 05:16:59 +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 Bugfix: with-pvars must be called after binding the pvar, not before. 2017-01-28 05:16:38 +01:00

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.