Re: $0 inconsistency?

If your tooling depends on the value of $0, note that $0 can be changed.

{
    local $0 = 'my program';
    print $0;     # my program
    system 'ps';  # <- works even here, at least on my Linux box.
}
print $0;     # Back to the old values.
system 'ps';  # ditto
[download]

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

Comment on Re: $0 inconsistency? Select or Download Code

Replies are listed 'Best First'.
Re^2: $0 inconsistency? by Perlbotics (Archbishop) on Apr 13, 2022 at 17:46 UTC
Seems Linux specifc with a 16 byte limit as explained here (Perl 5.14 delta): Assignment to $0 sets the legacy process name with prctl() on Linux	[reply]
Re^3: $0 inconsistency? by mr_mischief (Monsignor) on Apr 13, 2022 at 18:34 UTC
Eh... not quite. Setting `argv[0]` in the process should work on most POSIX systems. That change is an additional thing it does for Linux, and notes the limit for that. This is on a Mac.: `$ perl -e '$0="my really awesome process name"; sleep 60;' & [1] 73413 $ ps PID TTY TIME CMD 70164 ttys002 0:00.05 /opt/local/bin/bash 677 ttys004 0:05.06 /opt/local/bin/bash 73413 ttys004 0:00.03 my really awesome process name` [download]	[reply] [d/l] [select]
Re^2: $0 inconsistency? by misterperl (Friar) on Apr 15, 2022 at 12:59 UTC
tyvm I just copied it in case somewhere else it expected it otherwise: `$_=$0; s\|.+/\|\|;` [download] Cheers thx for the thoughtful reply!	[reply] [d/l]