-
- Downloads
consistently use 'loc' instead of 'range' to describe source locations
The problem with 'range' is that this word has a much more general meaning, it could be an integer range; typically it is also used in comments to describe range of levels or scopes. In the context of Menhir, which is centered on parsing, 'range' clearly associates with 'source range'. But for more general project this association is lost and 'range' is confusing.
parent
e31e8032
No related branches found
No related tags found
Showing
- client/F.ml 22 additions, 22 deletionsclient/F.ml
- client/F.mli 24 additions, 24 deletionsclient/F.mli
- client/FTypeChecker.ml 1 addition, 1 deletionclient/FTypeChecker.ml
- client/FTypeChecker.mli 2 additions, 2 deletionsclient/FTypeChecker.mli
- client/Infer.ml 22 additions, 15 deletionsclient/Infer.ml
- client/Infer.mli 2 additions, 2 deletionsclient/Infer.mli
- client/ML.ml 22 additions, 24 deletionsclient/ML.ml
- client/ML2F.ml 1 addition, 1 deletionclient/ML2F.ml
- client/MLParser.mly 29 additions, 24 deletionsclient/MLParser.mly
- client/Utils.ml 8 additions, 8 deletionsclient/Utils.ml
- client/Utils.mli 4 additions, 5 deletionsclient/Utils.mli
- client/bin/midml.ml 4 additions, 3 deletionsclient/bin/midml.ml
- client/test/CheckF.ml 1 addition, 1 deletionclient/test/CheckF.ml
- client/test/CheckML.ml 10 additions, 8 deletionsclient/test/CheckML.ml
- client/test/RandomML.ml 7 additions, 10 deletionsclient/test/RandomML.ml
- client/test/TestF.ml 19 additions, 21 deletionsclient/test/TestF.ml
- client/test/TestML.ml 89 additions, 91 deletionsclient/test/TestML.ml
- client/test/TestMLRandom.ml 3 additions, 3 deletionsclient/test/TestMLRandom.ml
- src/Solver.ml 43 additions, 43 deletionssrc/Solver.ml
- src/Solver.mli 12 additions, 13 deletionssrc/Solver.mli
Loading
Please register or sign in to comment