Re^3: ARGV empty when calling Perl from C program

thanks,this showed me the way.Perl was swallowing the very first argument and since I had just one followed by NULL, I could not see it

Comment on Re^3: ARGV empty when calling Perl from C program

Replies are listed 'Best First'.
Re^4: ARGV empty when calling Perl from C program by Lotus1 (Vicar) on May 24, 2014 at 14:32 UTC
I don't think Perl is doing it. I found this stackoverflow discussion where someone ran the unix program ps to show the running processes and it showed the value passed in `argv[0]` as the process name. So it looks like the os uses that first argument to allow you to have a nicer name than the full path it was invoked as. Thanks for posting the question, it was interesting to learn about and it got me to compile a c program for the first time in a long while, and on a Raspberry Pi at that.	[reply] [d/l]

Replies are listed 'Best First'.

Re^4: ARGV empty when calling Perl from C program
by Lotus1 (Vicar) on May 24, 2014 at 14:32 UTC

I don't think Perl is doing it. I found this stackoverflow discussion where someone ran the unix program ps to show the running processes and it showed the value passed in argv[0] as the process name. So it looks like the os uses that first argument to allow you to have a nicer name than the full path it was invoked as.

Thanks for posting the question, it was interesting to learn about and it got me to compile a c program for the first time in a long while, and on a Raspberry Pi at that.

[reply]
[d/l]