Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[kprint] - kprint lack of documentation and odd failure #1822

Closed
MirceaS opened this issue Feb 19, 2021 · 1 comment
Closed

[kprint] - kprint lack of documentation and odd failure #1822

MirceaS opened this issue Feb 19, 2021 · 1 comment
Labels
documentation
Projects
K frontend

Comments

@MirceaS
Copy link
Contributor

MirceaS commented Feb 19, 2021 •
edited

K Version

RV-K version 1.0-SNAPSHOT
Git revision: acf7ead
Git branch: master
Build date: Wed Feb 17 00:44:50 EET 2021

Description

kprint command doesn't recognize --version option and doesn't show a help menu when given --help but instead, on failure shows the message:
usage: kprint <definition.kore> <pattern.kore> [true|false|auto] [true|false] without explanation of what those last 2 options represent.

Additionally, after providing the two kore files to kprint, it still fails because it seems to interpret the input as directories:

> kprint test-memory-vdefinition.kore test-memory-spec.kore 
Cannot read file: test-memory-vdefinition.kore/syntaxDefinition.kore

Input Files

any kore file, I assume

Reproduction Steps

see above

Expected Behavior

A clearer description of how to use the command and why it looked for test-memory-vdefinition.kore/syntaxDefinition.kore in the example above.
@ehildenb ehildenb removed the bug label Feb 19, 2021
@ehildenb ehildenb changed the title [Bug] [kprint] - kprint lack of documentation and odd failure [kprint] - kprint lack of documentation and odd failure Feb 19, 2021
@ehildenb ehildenb added this to Selected for Development [PRODUCTIVITY] in K frontend Feb 23, 2021
zhengyao-lin pushed a commit to zhengyao-lin/k that referenced this issue Mar 20, 2021
@rv-jenkins
Update dependency: haskell-backend/src/main/native/haskell-backend (r…
eb5bc05 
…untimeverification#1291)

* haskell-backend/src/main/native/haskell-backend: 19f2d62e - Handle error entry types as exceptions (runtimeverification#1822)

* haskell-backend/src/main/native/haskell-backend: 764f9e57 - FreeVariables: Do not export constructor (runtimeverification#1820)

* haskell-backend/src/main/native/haskell-backend: 663a312f - include.mk: compatibility with Windows WSL2 (runtimeverification#1819)
@ehildenb ehildenb moved this from Selected for Development [NEXT RELEASE] to Selected for Development [2021 GOALS] in K frontend Apr 20, 2021
@ehildenb ehildenb moved this from Selected for Development [2021 GOALS] to Selected for Development [NEXT RELEASE] in K frontend Apr 20, 2021
@ehildenb ehildenb mentioned this issue Apr 20, 2021
Closed
7 tasks
@dwightguth
Copy link
Member

I am going to close this. People interested in invoking the unparser should instead use the new kore-print tool.

K frontend automation moved this from Selected for Development [NEXT RELEASE] to Done Dec 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation
Projects
No open projects
K frontend
  
Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dwightguth @MirceaS @ehildenb