Skip to content

Commit

Permalink
Remove references to xmlparsedata from docs (#723)
Browse files Browse the repository at this point in the history
  • Loading branch information
EagleoutIce authored Mar 14, 2024
2 parents baaa07a + a6127c8 commit 18141a9
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 13 deletions.
13 changes: 1 addition & 12 deletions wiki/Linting and Testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,18 +75,7 @@ npm run performance-test
See [test/performance](https://github.com/Code-Inspect/flowr/tree/main/test/performance) for more information on the suites, how to run them, and their results. If you are interested in the results of the benchmarks, see [here](https://code-inspect.github.io/flowr/wiki/stats/benchmark).

### Oh no, the tests are slow

If you have just installed *flowR* and *R* for the first time, the tests may take really long to run! If this is the case, please inspect the output for a banner informing you that the tests have to install a specific package (probably [`xmlparsedata`](https://cran.r-project.org/package=xmlparsedata)) — if this is the case ,it's probably best to install the package yourself, locally so that it can be found by *flowR* once.
For this, drop into the &nbsp *R* shell and issue:

```r
install.packages("xmlparsedata")
```

R&nbsp; may ask you if it should create a personal library, which you should confirm by typing `y` and pressing <kbd>enter</kbd> (it may ask again to create the package, answer this question with yes too). Afterwards you may have to select a mirror (any should be fine) and wait for the installation to finish. Once it is done, you can exit the R shell by typing `q()` and pressing <kbd>enter</kbd> (you do not have to save the workspace).
Now, the tests should run much faster!

If, however, you have already installed the package, or the tests are still too slow for your taste, you may want to check out how to [run only some of the tests](#running-only-some-tests).
If the tests are too slow for your taste, you may want to check out how to [run only some of the tests](#running-only-some-tests).

### Testing Within Your IDE

Expand Down
3 changes: 2 additions & 1 deletion wiki/Tokens.md
Original file line number Diff line number Diff line change
Expand Up @@ -147,10 +147,11 @@ While some of these tokens, like `COLON_ASSIGN`, are explicitly marked as deprec
| T61 || `{` | Groups expressions, no effect on scoping. |
| T62 || `}` | Corresponding end of `{`. |


## Tokens Representing Meta-Elements

| # || Token | Description |
|:----|:-:|:-------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------|
| T63 || `expr` | Represents an expression. |
| T64 || `expr_or_assign_or_help` | Used for example by `EQ-ASSIGN`, with the same semantics as `expr`. |
| T65 || `exprlist` | Added by [xml_parse_data](https://www.rdocumentation.org/packages/xmlparsedata/versions/1.0.5/topics/xml_parse_data) to group expressions. |
| T65 || `exprlist` | Added by [xml_parse_data](https://www.rdocumentation.org/packages/xmlparsedata/versions/1.0.5/topics/xml_parse_data) to group expressions, no longer used since [#659](https://github.com/Code-Inspect/flowr/pull/659). |

0 comments on commit 18141a9

Please sign in to comment.