Timeline for Parsing a command line
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2015 at 9:15 | comment | added | androschuk.a | You can try to use function FindCmdLineSwitch to parse parameters. See details on how it is work on youtube | |
| Nov 19, 2015 at 20:28 | comment | added | Jerry Dodge | @cpicanco Never had that problem on Stack Overflow. They insist on making examples as short as possible. That would be "beating around the bush". | |
| Nov 19, 2015 at 20:10 | comment | added | cpicanco | You increase your chances making life easier. Also, IMHO being explicit on usage is preferable. | |
| Nov 19, 2015 at 18:41 | answer | added | JosephStyons | timeline score: 2 | |
| S Nov 19, 2015 at 17:18 | history | suggested | cpicanco | Question includes non purely procedural pascal code. | |
| Nov 19, 2015 at 17:18 | comment | added | Jerry Dodge | @cpicanco That should be common sense with any object... | |
| Nov 19, 2015 at 17:07 | comment | added | cpicanco | FCmdLine := TCmdLine.Create; FCmdLine.AsString := '"C:\MyApp.exe" "C:\SomeFile.txt" -n -o "Some Value With Spaces" -f SomeOtherValueWithNoSpaces -p'; WriteLn(FCmdLine.AsString); ReadLn; | |
| Nov 19, 2015 at 16:41 | comment | added | cpicanco | Your sample usage is broken, you should create the object first. Could you edit your question? | |
| Nov 19, 2015 at 16:37 | review | Suggested edits | |||
| S Nov 19, 2015 at 17:18 | |||||
| Nov 18, 2015 at 15:31 | history | edited | Jerry Dodge | CC BY-SA 3.0 | added 225 characters in body |
| Nov 18, 2015 at 4:08 | history | edited | Jerry Dodge | CC BY-SA 3.0 | added 313 characters in body |
| Nov 18, 2015 at 3:32 | history | edited | Jerry Dodge | CC BY-SA 3.0 | added 114 characters in body; edited title |
| Nov 18, 2015 at 3:30 | history | edited | Jamal | CC BY-SA 3.0 | edited title |
| Nov 18, 2015 at 3:28 | history | asked | Jerry Dodge | CC BY-SA 3.0 |