This is an old revision of this page, as edited by Widefox(talk | contribs) at 14:37, 2 August 2020(Assessment (Start/Low): Computer science, +Computing (Rater)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.Revision as of 14:37, 2 August 2020 by Widefox(talk | contribs)(Assessment (Start/Low): Computer science, +Computing (Rater))
This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science
This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Reading about "parsing" I expected to read something about parsing command line arguments, probably in different programming languages, for example pointers to libraries that simplify this task for the most common conventions for the syntax of command lines. However, this article seems only to show how to access and iterate through the command line in different programming language. So at this point in time a less confusing title probably was "Command-line argument processing". — Preceding unsigned comment added by Pia F. Bichsel (talk • contribs) 10:18, 27 January 2016 (UTC)[reply]
Why this article doesn't make much sense and should either be reworked completely or deleted
The overall method used to parse command-line arguments is not a question of any particular programming language. For example, if you want your program to parse command-line arguments in a POSIX-compliant way, then the parser needs to do what POSIX specifies, regardless of the language it is written in. The language-specific part is merely how to accomplish what the specification says in $language.
In the examples for C, Bash, Perl and Python, there is exactly zero parsing going on. Parsing means syntactical analysis, not merely printing back user input. The example for Bash doesn't offer anything but an example of how user input should not be handled (unquoted substitutions), which is why I will remove it in a minute. If you want to know something about parsing command-line arguments in Bash, see, for example: https://mywiki.wooledge.org/BashFAQ/035.