Thanks for the response!
Use $Tombstone in place of $dog as the example of a perl variable in the script that throws an error.
It looks like I'd use %ENV on the UNIX shell variable $fruit. Is that true or am I to use the %ENV on the perl variable $tombstone?
Also I like the idea of going all Perl or calling an entire Perl script. The trouble is we are an all UNIX shell shop and If I started throwing Perl scripts around it would blow peoples minds. I don't want to stir that up. I just want to be able to access perl from time to time to use it's vast array of functions instead of using awk or exp or something else. For example UNIX doesn't have an index function that returns the positional value of a string when fed. But Perl does! So just simple "one offs" like that are what I'd want to use this for.
In reply to Re^2: assigning a perl variable in shell
by scheidr
in thread assigning a perl variable in shell
by scheidr
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |