- changed status to open
- assigned issue to
- removed comment
Use Piraha to Parse all CCL files
Piraha should be used to parse all the CCL files. This would give us a well-defined grammar and the ability to let other tools use the CCL files in a reliable way.
Keyword:
Comments (15)
-
reporter -
- changed milestone to Cactus_4.4.0
- removed comment
-
- removed comment
Is this going anywhere?
-
reporter - removed comment
See the piraha_everywhere branch of the flesh. https://bitbucket.org/cactuscode/cactus/pull-requests/28/piraha_everywhere/diff#comment-21446872
-
- removed comment
Just a note that the proposed branch seems to work well also with the Parma-thorns (compilation runs through and no new tests fail compared to master branch).
-
- removed comment
To be included in the flesh it should ideally adhere to the flesh coding standards, see #1520 .
-
- removed comment
Piraha is now used but does not adhere to the flesh coding standards.
-
- removed comment
Piraha's source code should be cleaned up so that it adheres to the flesh coding standards.
-
reporter - removed comment
I'd thought I'd done this. Can you point me to the coding standards you want me to adhere to? Thanks.
-
- removed comment
Please see: https://bitbucket.org/cactuscode/cactus/raw/387fae8c18ff04c3368f038d708b801b94e1ca2f/doc/MaintGuide.pdf section A2 in particular the grdoc headers and the indentation rules.
-
- removed comment
Also please see the comments in #1520 which points to the online version of the maintainers guide as well as naming conventions for internal functions.
-
- changed milestone to ET_2019_10
- edited description
-
- changed milestone to ET_2020_04
-
- changed milestone to ET_2020_05
-
- changed milestone to ET_2020_11
- Log in to comment