Allow each command to define an error string, access it when there is a Syntax Error.
Nobody has claimed this yet.
- Dominant language
- Assembly
- Stars
- 19
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Instead of just writing "SYNTAX ERROR" when the command doesn't work as expected, provide a short message that shows the usage of the command.
Each command would hold a string at the beginning or end that contains the error message, which the PATH program would access (using absolute address location or running the CMD with a flag to show the usage message).
Example:
] COPY A B
USAGE ERROR: COPY <FILE1>, <FILE2>
]COPY A, B
]REM SUCCESS
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the PATH program and command-specific usage messages but no source files or tests. Start by locating command dispatch and the existing SYNTAX ERROR path, then determine how command definitions and error output are organized. Done means invalid command usage displays that command's short usage string, as in the COPY example.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100