Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
I'm a beginner in learning programming. I ask about using the string array in main method as a parameter. Why not writing the Main() method without the string array? What is the point of having this array in Main method?
For example:
public static void Main(string[] args)
{
Console.WriteLine(args.Length);
Console.WriteLine(args[1]);
}
Console applications predate GUI applications, and these take command-line parameters for very long time (at least from CP/M time, which preceded MS-DOS, which preceded Windows, which preceded Windows NT — all preserving more or less the same logic).
You can pass command-line parameters to Windows GUI apps, too.
These are the args.
int main(int argc, char * argv[]).
Dec 16, 2014 at 8:45
c#, so it's [mostly] about Windows, and Windows's lineage starts with CP/M and does not cross with Unix.
foo /h that people were used to.
This is not the sole province of "old" console (command line) applications. Every running program has a "command line" that points at the executable image and includes any command line parameters. Plenty of GUI apps take arguments that alter either their initialization behavior or runtime behavior or both.
Most languages do let you specify an entry-point function that takes no arguments. But virtually all of them also allow you to pass arguments. This args array is simply an ordered collection of whatever is passed on the command line after the name of the executable file when the program is executed. EDIT: And of course in the case of the C language (as one example), the first argument (index 0) is actually the name of the program.
For example, imagine a pointless little program that displays a message in a message box, and lets you specify the message and the title for the window on the command line, like this:
myprogram.exe -title Foo -message Bar
Your args array in this case will look like this, presuming a language like C# which does not include the program name in the args array:
args[ 0 ] = "-title"
args[ 1 ] = "Foo"
args[ 2 ] = "-message"
args[ 3 ] = "Bar"
Making sense of the order of the arguments, and which ones are valid or not, is totally up to your own application code.
argc in C may be zero. in case of non-zero argc, argv[0] shall be a string that represents the "program name", or an empty string if the name is not available from the host environment. There is no requirement anywhere that it shall be a "full executable path". This is all from C99 section 5.1.2.2.1. Even your non-normative URL says this.
Dec 15, 2014 at 11:49
Have you ever listed items in a directory using
ls -a ~/Downloads
or
dir C:\Users\user1\Downloads\ /P
Now those "ls" and "dir" are commands/programs and the latter arguments are passed to the programs as string[] argv or sometimes int argc, char** argv. They provide arguments to the programs so they can behave accordingly.
When you start a program the OS loads the program to the memory and pushes the arguments to the stack. Now they are available to the program to be used.
High-level languages give you an easy way to access those arguments on the stack (as string arrays or an array of pointers to null terminated strings). If you used assembly, you would need to do some pointer arithmetic and load the arguments from stack to registers when you needed them.
For more details checkout following link, good explanation: FreeBSD Command Line Arguments
