-
Notifications
You must be signed in to change notification settings - Fork 20
Find all Input types that are hard to parse #853
Copy link
Copy link
Open
Labels
code improvementA feature request that will improve the software and its maintainability, but be invisible to users.A feature request that will improve the software and its maintainability, but be invisible to users.documentationImprovements or additions to documentationImprovements or additions to documentationparsers are hardExamples of where MCNP syntax is complicated and should be simplified.Examples of where MCNP syntax is complicated and should be simplified.
Description
Metadata
Metadata
Assignees
Labels
code improvementA feature request that will improve the software and its maintainability, but be invisible to users.A feature request that will improve the software and its maintainability, but be invisible to users.documentationImprovements or additions to documentationImprovements or additions to documentationparsers are hardExamples of where MCNP syntax is complicated and should be simplified.Examples of where MCNP syntax is complicated and should be simplified.
Recently we have introduced "parsing jail", that ignores inputs that are not easy to parse, and need custom parsers, and prevents them from causing errors.
So far this process has relied on user reports and adding inputs are essentially "one-offs".
We should go through the whole MCNP manual and identify all input types that should be "jailed".
Also we should make a list of these input types in the documentation.