* Santhosh Ram Manohar <santhosh....@gmail.com> [170601 14:03]:
>
>
> On Thursday, June 1, 2017 at 10:45:56 AM UTC-7, Jan Mercl wrote:
> >
> > On Thu, Jun 1, 2017 at 7:41 PM Santhosh Ram Manohar <santho...@gmail.com
> > <javascript:>> wrote:
> >
> > > Args: []string{"self", "selftest"},
> >
> > Here you explicitly pass arsg[0] == "self" and that's what the program
> > gets.
> >
>
> Yes, because I already have the program name in "Path". When Run() calls
> exec syscall i would expect Args[0] to be program name because from the
> exec point of view its no different from how shell would invoke it, no ?
The documentation for Args says:
// Args holds command line arguments, including the command as Args[0].
// If the Args field is empty or nil, Run uses {Path}.
//
// In typical use, both Path and Args are set by calling Command.
If you use Command, and then print the Args field, you see the proper
setup for Args. Try https://play.golang.org/p/phIbvlwa8s
Run is using Path as the command to execute and Args as the argv
argument to the underlying execve call (or corresponding Windows API).
The documentation for execve explicitly says that by _convention_ the
first string in argv (argv[0]) should contain the filename associated
with the file being executed. However, this is just convention, and the
caller of execve is not required to do so. Not setting argv[0] (i.e.
Args[0]) to the name of the command will normally get undesired results,
since all well-written programs expect argv[0] to be the command name,
not the first command argument.
...Marvin
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
