Skip to content

Allow each command to define an error string, access it when there is a Syntax Error. #9

Description

@22samurai

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions