Closed rohan221102 closed 1 year ago
I'm currently rewriting the project as a front-end to the GCC compiler. I will be putting this PR on hold for the time being.
👍
On Mon 15 Aug 2022 at 14:28, zeim839 @.***> wrote:
@.**** commented on this pull request.
In README.md https://github.com/rintolang/rinto/pull/6#discussion_r945599960:
-Watch this thread to see how this development goes! +# Website +rintolang.github.io
Can you also add the website on the repository's about section?
— Reply to this email directly, view it on GitHub https://github.com/rintolang/rinto/pull/6#pullrequestreview-1072469892, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKQCXXGBXBOIY47Y56BHYKDVZILUTANCNFSM545EMLWQ . You are receiving this because you were assigned.Message ID: @.***>
Firstly, remove the process and cmd folders. The entirety of the cmd package's functionality should (and easily can) be concentrated into a single pair of
cmd.h
andcmd.cpp
files.The help section should look like this:
Note the usage section, a command (an option from "the commands are" section) appears first, then a series of flags follows. So a call to the rin command line application is essentially a single command and then a series of flags. A flag is any word that begins with '--' or '-'.
Given this, the 'cmd.h' file should look like so:
Each available command (help, scanner) should be accompanied by a CmdHelp. The CmdHelp keeps its short description (to be printed on
rin help
) and its long description (printed when user callsrin help <command>
. If CmdHelp definitions prove to be tedious/repetitive, you may want to create a separate flags.h file.@rohan221102